Comment 19 for bug 1972762

I would just like to add another angry, frustrated, and probably redundant comment: I've been using Ubuntu since 2005, after switching from Debian because Ubuntu worked better out of the box for basic things like WiFi or watching videos. Over the years I've been very happy with Ubuntu, but now several times in the last few years I'm running into the problems caused by permissions in Snap (in the past for files in /tmp with pdftk, and now for files in ~/.<whatever> with Firefox). The answer always seems to be that the brokenness is "by design", but I don't understand why making something broken "by design" makes it okay: it's still broken, it's still a regression. And then there doesn't seem to be any way to simply disable the security mechanisms that are breaking these Snap packaged apps (e.g. here the solution, apparently, is to install Firefox from the Mozilla PPA as a regular .deb). I just want the Snap apps to be able to read files in /tmp and ~/.<whatever>. Why is this so hard?

Also, not only are these permission errors super annoying, they're also very confusing. They happen rarely, so I always seem to get confused and go through the same process:
1) get permission error about some file.
2) open terminal and check permissions of file: I have read access.
3) attempt to access file again from app and get same permission error.
4) Google the problem and find that it's caused by broken Snap permissions, where I didn't even know the app in question was managed by Snap (why would I, I used apt to install it ...).

Snapcraft: more like "crap snaf'd" :/