yes that is the output that is expected for those two commands when the kernel isn't patched.
aa-status - has a bug where it is incorrectly reporting it does not have privilege to read the profile set. It is mis-interpreting the failure to find the profiles file as a denial to access it. restart - will warn about network rules not being able to be enforced by the kernel but that will not affect the actual reload. In this case removal can't happen as the restart command can't determine which profiles exist in the kernel vs. what profiles exist in /etc/apparmor.d/ It will load all the profiles that exist in apparmor.d but can't remove from the kernel a profile that was removed from apparmor.d/ in this case you have to explicitly tell apparmor you removed it from the directory by using apparmor_parser -R on the file before removing it from apparmor.d/ or hitting the low level interface. Looking forward to the results from the reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1187970 Title: apparmor prevents custom printer driver from executing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1187970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
