apparmor.service fails to start when apt install/remove snapd due to snapd profile error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Confirmed
|
High
|
Unassigned | ||
snapd (Ubuntu) |
Triaged
|
High
|
Unassigned | ||
Cosmic |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
On Bionic (18.04) and others, running:
systemd 239-7ubuntu10.13
snapd 2.37.4+18.10.1
kernel 4.18.0-17.18,
the apparmor systemd service fails to start:
$ systemctl status apparmor.service
● apparmor.service - AppArmor initialization
Loaded: loaded (/lib/systemd/
Active: failed (Result: exit-code) since Wed 2019-04-17 18:00:06 CEST; 9s ago
Docs: man:apparmor(7)
http://
Process: 1295 ExecStart=
Main PID: 1295 (code=exited, status=123)
Looking at the logs it seems to be cause by the following error:
Apr 17 17:44:18 autopkgtest apparmor[358]: AppArmor parser error for /var/lib/
I will attach the full log from the service.
Hello
Is this bug reproducible? I'm running cosmic and I'm not seeing this at all.
The error would happen when the directory /var/lib/ snapd/apparmor/ snap-confine is absent but said directory is a part of the package *and* is created by snapd on demand.