[Bug 1440501] [NEW] Can not load mysql-akonadi apparmor profile

[Benedikt]

Public bug reported:

Apparmor fails to start witch exit code 123, because it can not load the
mysql-akonadi profile:

% sudo systemctl status apparmor -l      
● apparmor.service - LSB: AppArmor initialization
   Loaded: loaded (/etc/init.d/apparmor)
   Active: failed (Result: exit-code) since So 2015-04-05 12:29:33 CEST; 55s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 13906 ExecStart=/etc/init.d/apparmor start (code=exited, status=123)

Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld-akonadi in /etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 'local/usr.sbin.mysqld-akonadi'
Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld-akonadi in /etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 'local/usr.sbin.mysqld-akonadi'
Apr 05 12:29:33 benediktZ50-70 apparmor[13906]: ...fail!
Apr 05 12:29:33 benediktZ50-70 systemd[1]: apparmor.service: control process exited, code=exited status=123
Apr 05 12:29:33 benediktZ50-70 systemd[1]: Failed to start LSB: AppArmor initialization.
Apr 05 12:29:33 benediktZ50-70 systemd[1]: Unit apparmor.service entered failed state.
Apr 05 12:29:33 benediktZ50-70 systemd[1]: apparmor.service failed.

However Apparmor loaded successfully:

% sudo aa-status
apparmor module is loaded.
17 profiles are loaded.
17 profiles are in enforce mode.
   /sbin/dhclient
   /usr/lib/NetworkManager/nm-dhcp-client.action
   /usr/lib/NetworkManager/nm-dhcp-helper
   /usr/lib/connman/scripts/dhclient-script
   /usr/lib/cups/backend/cups-pdf
   /usr/lib/libvirt/virt-aa-helper
   /usr/lib/telepathy/mission-control-5
   /usr/lib/telepathy/telepathy-*
   /usr/lib/telepathy/telepathy-*//pxgsettings
   /usr/lib/telepathy/telepathy-*//sanitized_helper
   /usr/lib/telepathy/telepathy-ofono
   /usr/sbin/cups-browsed
   /usr/sbin/cupsd
   /usr/sbin/cupsd//third_party
   /usr/sbin/libvirtd
   /usr/sbin/tcpdump
   docker-default
0 profiles are in complain mode.
5 processes have profiles defined.
5 processes are in enforce mode.
   /sbin/dhclient (11821) 
   /usr/lib/telepathy/mission-control-5 (2008) 
   /usr/sbin/cups-browsed (840) 
   /usr/sbin/cupsd (12783) 
   /usr/sbin/libvirtd (971) 
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.

It is really necessary to set Apparmor as failed if one profile could
not be loaded?

** Affects: akonadi (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: apparmor (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: kubuntu vivid

** Also affects: akonadi (Ubuntu)
   Importance: Undecided
       Status: New

** Tags added: kubuntu vivid

** Summary changed:

- Can not load mysql-akonadi profile
+ Can not load mysql-akonadi apparmor profile

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to akonadi in Ubuntu.
https://bugs.launchpad.net/bugs/1440501

Title:
  Can not load mysql-akonadi apparmor profile

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