undefined | Better HN

0 points_y5hn5y ago0 comments

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.

0 comments

4 comments · 2 top-level

personalcompute5y ago· 2 in thread

I 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.

lokedhs5y ago

There 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

silon425y ago

Yup. 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.

totetsu5y ago

For 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 ..

j / k navigate · click thread line to collapse