*** This bug is a duplicate of bug 447292 ***
https://bugs.launchpad.net/bugs/447292
Is this really a dupe of bug #447292 (which is "AppArmor does not allow
access when @{HOME} is not /home")? This bug is reporting some problems
with the evince apparmor profile, since it forbids some actions that
evince legitimately wants to do (access recent files, connect to session
management). And this can't be fixed by adjusting apparmor tunables to
deal with a different home directory location -- it happens even with a
totally standard /home/user directory. Furthermore, it's not even a bug
in apparmor -- it's a problem with the apparmor files shipped in the
evince package.
--
karmic evince apparmor profile is too strict -- can't start on clean install
https://bugs.launchpad.net/bugs/475675
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
