Responding to myself: "There is definitely a usability issue though because Seb is right-- it is a core feature of strict confinement that snaps cannot see other snaps, files, etc, but file choosers need to be able to do so and adding a rule like the one above breaks that. Adding another transitional interface to allow filesystem browsing and/or adjust home is possible...."
FYI, the removable-media interface has allowed reading dirs for /run, /run/media and /media while the default template has allowed reading /home/ and / since 2.29 (see https://forum.snapcraft.io/t/application- cant-see-media-in-file-browser/2384/9). This means that vlc, etc can navigate from $HOME -> /home -> / -> /media -> ... without any usability issues. In 2.31 we adjusted the transitional home interface to allow reading ~/snaps. Since snaps start in $SNAP_USER_DATA (~/snap/<name>/<revision>), this means that a snap can navigate from $HOME/snap/<name>/<revision> -> $HOME/snap/<name> -> $HOME/snap -> $HOME. Between these two items, traditional file choosers should now operate without usability issues. Which is this bug. As such, marking as Fix Released. ** Changed in: snapd (Ubuntu) Status: In Progress => Fix Released ** Changed in: snapd (Ubuntu) Assignee: Zygmunt Krynicki (zyga) => Jamie Strandboge (jdstrand) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643706 Title: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
