control: reopen -1 Hello Vincas,
if you belive this issue isn't solved we can should reopen this report. On Tue, Jan 02, 2018 at 08:19:21PM +0200, Vincas Dargis wrote: > Uhm, why this bug was marked as Done? > > I have just upgraded some Jessie machine and got error (as expected) during > upgrade: > > ``` > AppArmor parser error for /etc/apparmor.d/usr.bin.thunderbird in > /etc/apparmor.d/usr.bin.thunderbird at line 12: syntax error, unexpected > TOK_SET_VAR, expecting TOK_OPEN > ``` > > Restarting AppArmorm fails: > > `` > sudo systemctl restart apparmor > Job for apparmor.service failed. See 'systemctl status apparmor.service' and > 'journalctl -xn' for details. > ``` > > ``` > $ sudo journalctl -xn > -- Logs begin at An 2018-01-02 20:06:14 EET, end at An 2018-01-02 20:17:16 > EET. -- > Sau 02 20:17:13 dev-debian8kde systemd[1]: Starting LSB: AppArmor > initialization... > -- Subject: Unit apparmor.service has begun with start-up > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit apparmor.service has begun starting up. > Sau 02 20:17:13 dev-debian8kde apparmor[7100]: Starting AppArmor > profiles:AppArmor parser error for /etc/apparmor.d/usr.bin.thunderbird in > /etc/apparmor.d/usr.bin.thunderbi > Sau 02 20:17:13 dev-debian8kde apparmor[7100]: AppArmor parser error for > /etc/apparmor.d/usr.bin.thunderbird in /etc/apparmor.d/usr.bin.thunderbird > at line 12: syntax error > Sau 02 20:17:14 dev-debian8kde apparmor[7100]: failed! > Sau 02 20:17:14 dev-debian8kde systemd[1]: apparmor.service: control process > exited, code=exited status=123 > Sau 02 20:17:14 dev-debian8kde systemd[1]: Failed to start LSB: AppArmor > initialization. > > ``` Is this only happen on a Jessie system? I just ask for setting up the correct tags on this report. Regards Carsten
