> I'm trying to investigate this from AppArmor angle now. Good insight! That solved it!
I found that my apparmor profile did indeed _not_ contain `fowner`. It looks like an update on the 10th of Oct. failed to overwrite the old apparmor profile and left a .dpkg-dist version of the new profile: # stat /etc/apparmor.d/usr.lib.snapd.snap-confine.real.dpkg-dist File: /etc/apparmor.d/usr.lib.snapd.snap-confine.real.dpkg-dist Size: 31877 Blocks: 64 IO Block: 4096 regular file Device: 252,1 Inode: 20712107 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2025-10-17 09:41:03.809489878 +0200 Modify: 2025-07-25 13:18:47.000000000 +0200 Change: 2025-10-10 14:12:12.907670945 +0200 Birth: 2025-10-10 14:12:10.608670725 +0200 So this solves it: ``` # back-up old, just in case: sudo mv /etc/apparmor.d/usr.lib.snapd.snap-confine.real /etc/apparmor.d/usr.lib.snapd.snap-confine.real.bak sudo mv /etc/apparmor.d/usr.lib.snapd.snap-confine.real.dpkg-dist /etc/apparmor.d/usr.lib.snapd.snap-confine.real ``` reboot (systemctl reload wasnt enough for me). Now everything works again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127224 Title: all snaps fail to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2127224/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
