| 2019-04-18 07:13:12 |
Kleber Sacilotto de Souza |
bug |
|
|
added bug |
| 2019-04-18 07:13:12 |
Kleber Sacilotto de Souza |
attachment added |
|
apparmor.service.log https://bugs.launchpad.net/bugs/1825298/+attachment/5256650/+files/apparmor.service.log |
|
| 2019-04-18 07:14:12 |
Kleber Sacilotto de Souza |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-04-18 07:14:12 |
Kleber Sacilotto de Souza |
bug task added |
|
snapd (Ubuntu Cosmic) |
|
| 2019-04-18 07:14:38 |
Kleber Sacilotto de Souza |
summary |
apparmos.service fails to start on Cosmic due to snapd profile error |
apparmor.service fails to start on Cosmic due to snapd profile error |
|
| 2019-10-15 13:57:18 |
Zygmunt Krynicki |
bug task added |
|
snapd |
|
| 2019-10-16 05:43:38 |
Michael Vogt |
snapd (Ubuntu Cosmic): status |
New |
Won't Fix |
|
| 2019-10-16 05:43:44 |
Michael Vogt |
snapd: status |
New |
Triaged |
|
| 2019-10-16 05:43:47 |
Michael Vogt |
snapd: importance |
Undecided |
High |
|
| 2019-10-16 05:43:49 |
Michael Vogt |
snapd (Ubuntu): status |
New |
Triaged |
|
| 2019-10-16 05:43:52 |
Michael Vogt |
snapd (Ubuntu): importance |
Undecided |
High |
|
| 2019-10-16 05:44:21 |
Michael Vogt |
description |
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. |
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/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. |
|
| 2019-10-16 05:44:44 |
Michael Vogt |
summary |
apparmor.service fails to start on Cosmic due to snapd profile error |
apparmor.service fails to start when apt install/remove snapd due to snapd profile error |
|
| 2019-10-16 06:17:42 |
Zygmunt Krynicki |
snapd: status |
Triaged |
Confirmed |
|
