Disk mount point is in /media tree. Mount point owner changed to user who starts Firefox snap.
It was verified also that all processes started as Firefox snap run under same user.
Downloads from web sides visited using Firefox can’t be stored to mentioned disk with mount point in /media tree although snap connections firefox command output
presents firefox:removable-media in column plug yet :removable-media in column slot - for command output line removable-media. This is connection is established automatically at system start.
It doesn’t help to disconnect Firefox from removable-media slot then reconnect it manually.
No problems to save downloaded files to home directory.
You’re right myself missed this detail. Sorry for that.
Yes, user can store download to home subfolder named Downloads then copy it to addressed sub-directory of /media using operating system GUI file explorer.
What error does firefox display when it fails to write to that location under /media ?
Can you check for apparmor denials in the system journal when that happens? (you can run journalctl -f | grep DEN in a terminal while reproducing the problem, and share the relevant output here)
User encounters presented problem regardless which favor of Download settings or favor of download proceeding is used. In both areas addressed is only storing to disk file, never opening in document viewer.
Something like “you are not rights to save to that location” or similar sounding (sorry I didn’t memorized exact text flow). Journal will be checked for apparmor logs at next nearest occasion - thanks for the hint. Reporting will follow.
I course of troubleshooting administrator teared down once the automatic connection firefox snap to removable-media plug. It was made in order to see if there is any difference if interface is built manually. Afterwards one can have manual setup of interface or no interface. Automatic interface setup is no more working. How to restore automatic interface setup?