Public bug reported: When apparmor prevents something from running, it doesn't notify the user. I expected it to notify the user via a popup or something similar.
In my case, I wrote a Firefox plugin that opens an editor (like emacs or gvim) with the contents of the textarea. A user was able to configure it to use gedit, but not sublime-text-2; sublime-text-2 would return an exit code 1 and just fail to start. see https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/882125 for the details. Long story short; If a simple dialog had popped up and said "AppArmor prevented sublime-text-2 from running" then it would have saved all our time: The users, mine, and the gentleman who helped on the above bug. If that isn't feasible then maybe having it exit with a non-standard exit code (say, 126 or something) then we could have googled that. ** Affects: apparmor (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/882213 Title: Apparmor doesn't notify user of "enforcements" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/882213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
