Package: snapd Severity: important Version: 2.20-2 Hello,
On a clean stretch install, booted with apparmor enabled (security=apparmor apparmor=1), snapd fails to run due to apparmor failures. It appears to be caused by the fact that /lib is a symlink to /usr/lib, with the symlinks getting resolved and so failing because the apparmor profile only contains /lib paths. There is that and a failure to execute snap-exec if I remember correctly. It'd be great to have this fixed as snapd will very actively try to use apparmor if it's enabled in the kernel. To the point where disabling the apparmor profiles for snapd leads to another failure as snapd fails to manually change profile then. Stéphane
signature.asc
Description: PGP signature
