I'm affected by this on Ubuntu 24.04 - this has become more of an issue
now that Ubuntu seems to be moving more and more software to snaps
rather than regular packages
In my case I have /nfshome NFS mounted via /etc/fstab, and symlinks from
various folders in ~ e.g. ~/Documents -> /nfshome/myuser/Documents
I have updated /etc/apparmor.d/tunables/home.d/ubuntu (via 'sudo dpkg-
reconfigure apparmor') to add /nfshome to @{HOMEDIRS} and restarted
apparmor.service and snapd.service - I've even restarted the whole
machine - but When launching a strictly confined snap I can't even see
the /nfshome folder, and can't access my documents.
Is snapd intended to work with directories that are mounted over NFS? I
haven't used snapd apart from as a part of Ubuntu but it feels like
there should be a way of specifying 'trusted locations' otherwise how
would snap apps open files? Updating @{HOMEDIRS} doesn't seem to have
worked in my case.
I can see a bunch of apparmor DENIED calls, including:
dbus-daemon[9937]: apparmor="DENIED" operation="dbus_signal" bus="session"
path="/" interface="org.kde.KDirNotify" member="enteredDirectory" mask="send"
name="org.freedesktop.DBus" pid=15371 label="snap.freecad.freecad"
peer_pid=10412 peer_label="unconfined"
kernel: audit: type=1400 audit(1729199241.759:3007): apparmor="DENIED"
operation="open" class="file" profile="snap.freecad.freecad" name="/etc/fstab"
pid=15371 comm="FreeCAD" requested_mask="r" denied_mask="r" fsuid=12345 ouid=0
and the file picker doesn't show the /nfshome folder at all, or any of the
~/Documents symlinks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662552
Title:
snaps don't work with NFS home
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1662552/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
