This is a very common bug report, see e. g. bug 429863 or bug 429880. Instead of trying to work arond this in a bazillion packages, is it possible to catch that situation in AppArmor itself and disable itself until the next boot into the karmic kernel?
** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: cups (Ubuntu) Assignee: Martin Pitt (pitti) => (unassigned) ** Changed in: apparmor (Ubuntu) Importance: Undecided => High ** Changed in: apparmor (Ubuntu) Status: New => Triaged ** Also affects: apparmor (Ubuntu Karmic) Importance: High Status: Triaged ** Also affects: cups (Ubuntu Karmic) Importance: Undecided Status: New ** Also affects: dhcp3 (Ubuntu Karmic) Importance: Undecided Status: New ** Also affects: evince (Ubuntu Karmic) Importance: Undecided Status: New ** Also affects: gdm-guest-session (Ubuntu Karmic) Importance: Undecided Status: New ** Also affects: tcpdump (Ubuntu Karmic) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu Karmic) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- /sbin/apparmor_parser: ... Profile doesn't conform to protocol https://bugs.launchpad.net/bugs/429872 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs