On 2019-10-20, Chris Green wrote: > On Sun, Oct 20, 2019 at 11:01:02AM +0200, Matthias Apitz wrote: >> El día domingo, octubre 20, 2019 a las 09:25:46a. m. +0100, Nuno Silva >> escribió: >> >> > On 2019-10-19, José María Mateos wrote: >> > >> > > On Sat, 19 Oct 2019 19:17:06 +0100 Chris Green <c...@isbd.net> wrote: >> > >> Running 'evince ~/.mitt/fred.pdf' displays the PDF file successfully >> > >> but running 'evince ~/.mutt/fred.pdf' produces a Permission Denied >> > >> message in a pop-up window. All directory names I have tried other >> > >> than .mutt allow the PDF file to be read. >> >> I can't reproduce this on FreeBSD. The OP could run on any Linux (don't >> know if the problem is on Linux): >> >> strace -o evince.tr -f evince ~/.mutt/fred.pdf >> >> and look into the file evince.tr which open(2) or stat(2) gives a >> Permission Denied and why. If the OP can't see this, he/she should >> post this file somewhere. >> >> matthias >> > I'm running xubuntu 19.04 on both systems which show this bug. I > don't have evince on any other system at the moment. > > I will try the strace and also I may try installing evince on a system > which is running xubuntu 18.04 to see if the bug is there too. > > Thanks everyone and listen to this space! :-)
Do these systems have apparmor? It seems to be some sort of security tool which restricts access to files and directories based on rules. I don't use ubuntu (or ubuntu-based) systems nor apparmor, but this looks like it might be related: https://gitlab.com/apparmor/apparmor/raw/master/profiles/apparmor.d/abstractions/private-files -- Nuno Silva
