AFAIU this happens when appamor.service is disabled and does not start
during the boot or there is no apparmor profile for snap-confine. Can
you make sure that `systemctl show apparmor.service` shows that it's
enabled, and attach the output of `sudo aa-status |grep snap-confine` ?
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971491
Title:
After reboot firefox refuses to run snap-confine has elevated
permissions and is not confined but should be. Refusing to continue to
avoid permission escalation attacks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1971491/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
