[Bug 1881294] Re: Apparmor blocks evince GUI-Input-Dialogs

2020-06-01 Thread Jamie Strandboge
*** This bug is a duplicate of bug 1856738 *** https://bugs.launchpad.net/bugs/1856738 @Reinhard, you are now hitting bug #1856738 which prevents @{HOME} from being used in the peer_addr for an abstract socket. For now, I suggest updating /etc/apparmor.d/abstractions/ibus to have: unix

[Bug 1881294] Re: Apparmor blocks evince GUI-Input-Dialogs

2020-06-01 Thread Reinhard
Hello Arnold, thanks a lot for your fast and good answer! But maybe I do something terribly wrong or there is something working strange? To deploy apparmor changes I started to play around on a test machine with no LDAP and no NFS. 1. created new user: /home/teachers/check 2. added

[Bug 1881294] Re: Apparmor blocks evince GUI-Input-Dialogs

2020-05-29 Thread Seth Arnold
Hello Reinhard, please see the /etc/apparmor.d/tunables/home.d/site.local file, it describes how to add additional paths to the @{HOMEDIRS} variable, which should allow evince, and all other profiles that use @{HOME}, to function in your environment. Thanks ** Changed in: evince (Ubuntu)