[Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a

[Rocko]

Thanks, removing the packages makes the errors go away.

Do you think the error message is misleading? Instead of saying "Failed
to start AppArmor initialization", perhaps it should say, "Failed to
load some profiles"?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1756800

Title:
  Failed to start AppArmor initialization with status=123/n/a

Status in apparmor package in Ubuntu:
  Won't Fix
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  AppArmor in Ubuntu 18.04 fails to start every time:

  $ 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 Mon 2018-03-19 13:47:22 AWST; 56s ago
       Docs: man:apparmor(7)
             http://wiki.apparmor.net/
    Process: 773 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)
   Main PID: 773 (code=exited, status=123)

  Mar 19 13:47:21 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e
  Mar 19 13:47:21 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
  Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.web
  Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e
  Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
  Mar 19 13:47:22 xps15-9560 apparmor[773]:    ...fail!
  Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a
  Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Failed with result 'exit-code'.
  Mar 19 13:47:22 xps15-9560 systemd[1]: Failed to start AppArmor initialization.

  
  journalctl -xe gives essentially the same lack of information issued after a systemctl restart apparmor.service.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apparmor 2.11.0-2ubuntu19
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Mar 19 13:50:42 2018
  InstallationDate: Installed on 2017-08-16 (214 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-12-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=1
  SourcePackage: apparmor
  Syslog:
   Mar 19 13:47:22 xps15-9560 dbus-daemon[1252]: [system] AppArmor D-Bus mediation is enabled
   Mar 19 13:47:23 xps15-9560 dbus-daemon[1491]: [session uid=125 pid=1491] AppArmor D-Bus mediation is enabled
   Mar 19 13:47:39 xps15-9560 dbus-daemon[2160]: [session uid=1001 pid=2160] AppArmor D-Bus mediation is enabled
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (121 days ago)
  mtime.conffile..etc.apparmor.d.abstractions.nameservice: 2017-10-24T16:47:24.395996

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