The initial report indicated a parser error, but then it was reported
that the apparmor package was removed, so then it would not be able to
run properly. I'm not able to reproduce with the information given. If
you are able to provide exact steps to reproduce, please do and we can
take another look.

** Changed in: snapd (Ubuntu)
       Status: New => Invalid

** Changed in: apparmor (Ubuntu)
       Status: New => Incomplete

-- 
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/1764312

Title:
  fails to start in Bionic

Status in apparmor package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  $ systemctl status apparmor
  ● apparmor.service - AppArmor initialization
     Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor 
preset: enabled)
     Active: failed (Result: exit-code) since Mon 2018-04-16 07:46:13 BST; 1h 
10min ago
       Docs: man:apparmor(7)
             http://wiki.apparmor.net/
    Process: 635 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 635 (code=exited, status=123)

  Apr 16 07:46:12 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:12 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.bin.firefox
  Apr 16 07:46:13 ev34 apparmor[635]: AppArmor parser error for 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in /etc/ap
  Apr 16 07:46:13 ev34 apparmor[635]: Skipping profile in 
/etc/apparmor.d/disable: usr.sbin.rsyslogd
  Apr 16 07:46:13 ev34 apparmor[635]:    ...fail!
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  Apr 16 07:46:13 ev34 systemd[1]: apparmor.service: Failed with result 
'exit-code'.
  Apr 16 07:46:13 ev34 systemd[1]: Failed to start AppArmor initialization.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1764312/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to