Public bug reported:
On Cosmic (18.10), 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/system/apparmor.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-04-17 18:00:06 CEST; 9s ago
Docs: man:apparmor(7)
http://wiki.apparmor.net/
Process: 1295 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
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/snapd/apparmor/profiles/snap-confine.core.6673 in
/var/lib/snapd/apparmor/profiles/snap-confine.core.6673 at line 11:
Could not open '/var/lib/snapd/apparmor/snap-confine'
I will attach the full log from the service.
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Affects: snapd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Attachment added: "apparmor.service.log"
https://bugs.launchpad.net/bugs/1825298/+attachment/5256650/+files/apparmor.service.log
** Also affects: snapd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Summary changed:
- apparmos.service fails to start on Cosmic due to snapd profile error
+ apparmor.service fails to start on Cosmic due to snapd profile error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825298
Title:
apparmor.service fails to start on Cosmic due to snapd profile error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1825298/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
