I uploaded 2.13.3-7ubuntu4 to address this:
https://launchpad.net/ubuntu/+source/apparmor/2.13.3-7ubuntu4
There might be other fixes for zsys, but this should address the issue
in snapd. It is currently in unapproved, but a member of the release
team will hopefully approve it soon.
** Changed in: apparmor (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: apparmor (Ubuntu Focal)
Milestone: None => ubuntu-20.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1871148
Title:
services start before apparmor profiles are loaded
Status in AppArmor:
Invalid
Status in apparmor package in Ubuntu:
Fix Committed
Status in zsys package in Ubuntu:
Confirmed
Status in apparmor source package in Focal:
Fix Committed
Status in zsys source package in Focal:
Confirmed
Bug description:
Per discussion with Zyga in #snapd on Freenode, I have hit a race
condition where services are being started by the system before
apparmor has been started. I have a complete log of my system showing
the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/.
Restarting apparmor using `sudo systemctl restart apparmor` is enough
to bring installed snaps back to full functionality.
Previously, when running any snap I would receive the following in the
terminal:
---
cannot change profile for the next exec call: No such file or directory
snap-update-ns failed with code 1: File exists
---
Updated to add for Jamie:
$ snap version
snap 2.44.2+20.04
snapd 2.44.2+20.04
series 16
ubuntu 20.04
kernel 5.4.0-21-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
