aa-status is part of the apparmor package
aa-disabled is part of the apparmor-utils package
the package split is done to reduce the install foot print to a minimum
for base installs, iso images etc.
The failure of the apparmor_parser -R is odd, perhaps the profile had
been already removed by a previous action? Profiles exist in two places
on the system, their text representation stored in the filesystem in
userspace and their binary representation in that is loaded into the
kernel, either during boot or package install, etc.
You can find out your loaded set of profiles via the aa-status command (root
privs required), or by directly poking the lower level interface. Either using
a simplied file based view
cat /sys/kernel/security/apparmor/profiles
or a slightly more detail directory based view
ls /sys/kernel/security/apparmor/policy/profiles/
Generally I would agree that you shouldn't disable apparmor, however I am a
pragmatist and believe security is useless if it prevents you from doing the
work you need to get done.
I am going to add a task for cups and see if the those more familiar
with cups have any ideas.
best of luck on your roll back.
** Also affects: cups (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1251973
Title:
Printing denied since upgrade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1251973/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
