This bug was fixed in the package apparmor - 2.10.95-0ubuntu2
---------------
apparmor (2.10.95-0ubuntu2) xenial; urgency=medium
* debian/patches/r3435-allow-dnsmasq-access-to-lxd-bridge.patch: Grant
access to the new default bridge configuration in LXD 2.0.0 (LP: #1566944)
* debian/patches/r3437-add-attach-disconnected-to-dnsmasq.patch: Add the
attach_disconnected flag to the dnsmasq profile in order to prevent a
disconnected path denial triggered by the latest network-manager upload
(LP: #1569316)
* debian/lib/apparmor/functions: Reference the new path used for snapd
AppArmor profiles to fix a bug which left those profiles unloaded after
booting (LP: #1569573)
-- Tyler Hicks <tyhi...@canonical.com> Tue, 12 Apr 2016 16:59:46 -0500
** Changed in: apparmor (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1569573
Title:
recent snapd path renames causes apparmor to not load profiles on boot
Status in Snappy:
Fix Committed
Status in apparmor package in Ubuntu:
Fix Released
Bug description:
/lib/apparmor/functions has this:
PROFILES_SNAPPY="/var/lib/snappy/apparmor/profiles"
The recent snappy path renames move the profiles to
/var/lib/snapd/apparmor/profiles so now snappy apparmor profiles are
not loading on boot.
apparmor needs this change:
PROFILES_SNAPPY="/var/lib/snapd/apparmor/profiles"
To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1569573/+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
