3 ms·
Snap can't seem to access my mounts. They're not very special mounts, but it happens in linux that you mount something, but snap just won't access. That made "n
by loopz 6y ago
Snap can't seem to access my mounts. They're not very special mounts, but it happens in linux that you mount something, but snap just won't access. That made "no-go" a no-brainer.
- personalcompute 6y agoI have the same problem. Snaps are confined to only files within $HOME. I keep almost all data under /media/ and this caused snaps to be mostly unusable for me, at least unusable for productivity apps where I need to process data. Some apps though are self contained, e.g. Spotify, for example, works fine for me as a snap. The limitation stems from a design problem, details at https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706 https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706.
- silon42 6y agoYup. There needs to be considerable work to integrate snaps from completely sandboxed (no access to file system/network/hardware), to giving them controlled access to some resources, managed/monitored by root and/or user.
- lokedhs 6y agoThere is also a problem where snapd fails if your home directory isn't called /home/username (i.e. if it's located in a different path). At this point snap sounds like a bad joke to me. Especially when Flatpak already exists. https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552
- totetsu 6y agoFor the longest time Snap chromium couldn't access files it had downloaded. So I would click to open a pdf when it was completed and get an error. I had to go whitelist my home dir in some config somewhere ..