Dear Krynicki,
Q: Do you have any AppArmor denials in your system log? A: Yes, but they are unrelated to snapd’s squashfs mounting. Most denials are from other services (cupsd, Xorg) or snap apps (Emote, Discord). There are no denials directly preventing snapd from mounting snaps. Q: Anything showing up with DENIED that looks related to snapd? A: No. The only snapd-related message was a snap-update-ns denial trying to bind mount /boot/, but this does not block normal snap operation. Disabling AppArmor does not make snapd work, indicating AppArmor is not the cause. Q: Is this a container or bare metal or virtual machine system? A: Bare metal system (systemd-detect-virt returns "none") Q: Are you using apparmor.d project with extra AppArmor profiles? A: Yes, 127 custom profiles are loaded, but they do not appear to block snapd. Q: Additional notes A: Snapd failing to mount snaps is likely due to squashfs/mount issues, such as missing kernel support for squashfs or loop devices, snap-confine helper issues, or the snaps being stored on a non-native filesystem. AppArmor does not appear to be responsible. Best Regards Armin Sent from Proton Mail for Android. -------- Original Message -------- On Wednesday, 11/26/25 at 10:45 Zygmunt Krynicki <[email protected]> wrote: W dniu 21.11.2025 o 15:20, Armin pisze: > Package: snapd > Version: 2.71-3 > Severity: important > File: /usr/bin/snap > X-Debbugs-Cc: [email protected] > > Dear Maintainer, Thank you for reporting this issue. At present I'm not quite sure what is going on. The kernel looks regular, I need to see if I can reproduce this myself. You might help me by answering a few questions: Q: Do you have any apparmor denials in your systmem log? Q: Anything showing up with DENIED that looks related to snapd? Q: Is this a container or a bare metal or virtual machine system? Q: Are you using apparmor.d project with extra apparmor profiles. I'm sorry for whatever the cause is, I understand this must be frustrating a little. Best regards Zygmunt Krynicki
