[Bug 1773223] Re: man -l local-file fails with Access Denied

2018-11-05 Thread Colin Watson
This is going to be a bit tricky. The intent of the AppArmor confinement we do is to leave /usr/bin/man itself mostly unconfined, but apply rather stricter confinement to groff-related subprocesses and decompression filters. It's easy enough to allow /usr/bin/man itself to read from the network

[Bug 1773223] Re: man -l local-file fails with Access Denied

2018-09-26 Thread Frank Denissen
My home directory is indeed on NFSv4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773223 Title: man -l local-file fails with Access Denied To manage notifications about this bug go to:

[Bug 1773223] Re: man -l local-file fails with Access Denied

2018-09-26 Thread Andrew McKinlay
Is your home directory on NFS? I am getting the exact same issue. Output of dmesg: ``` [4399566.994763] audit: type=1400 audit(1537967487.910:1582): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=5981 comm="man" laddr= lport=744 faddr= fport=2049 family="inet"