User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0

Steps to reproduce:

Saved a file to /tmp

Actual results:

File did not appear in /tmp

Expected results:

File appeared in /tmp

Olivier, as much as I can remember, Firefox Snap does not have access to the system's /tmp, right?

From https://bugzilla.mozilla.org/show_bug.cgi?id=1786392#c6 Firefox Snap cannot have access to /tmp/ itself.

If you are going to not fix it, where can the Snap FireFox write too ? Where is the list ? How do users discover locations they can pick in the download modal that will actually work ?

(In reply to tc from comment #3)

If you are going to not fix it, where can the Snap FireFox write too ? Where is the list ? How do users discover locations they can pick in the download modal that will actually work ?

As much as I can tell, /tmp/snap.firefox/tmp is the one you will get. The other questions should be raised to people working on Snap, I dont know the answers.

Err, OK, who are they and where ?

Maybe you should file a bug against xdg-desktop-portal's GNOME or GTK or other desktop environment you are using, so that the file picker should not present a directory that is not accessible ? There was already the same issue with Samba share mount points ...

As you can see, not a lot of activity against that: https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/issues/48

Ta, done https://bugs.kde.org/show_bug.cgi?id=458637