On Tue, 2017-02-28 at 15:59 +0100, Michael Biebl wrote:
2017-02-28 15:50 GMT+01:00 Chris <cpollock embarqmail com>:Hi Carlos, someone suggested, I think it was on the list, that an X process is changing the permission of /run/user/1000/dconf/user every 2There is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732209 (and all the duplicates) and related bug reports like https://bugzilla.redhat.com/show_bug.cgi?id=753882 https://bugzilla.redhat.com/show_bug.cgi?id=921689 Those are all a result of using "su <some X program using dconf>" As XDG_RUNTIME_DIR is not reset by su, dconf will happily change the permissions of the dconf files. I'm not saying that this is necessarily what's happening here just something you should check. Carlos is probably right, in this case it's more likely a sandbox issue.
Thanks for the links Michael, I saw the Debian bug report when I first started researching this issue. The problem with the su/gksu theory causing this is that I very, very seldom use gksu. At the very most maybe once a month if that. For some reason I keep looking at 'can't create' not realizing until it suddenly hits me that hey, dummy, the file is already there and all the permissions are correct so what seems to be the problem then. So why am I being told every two minutes that the file can't be created if it already exists? Chris -- Chris KeyID 0xE372A7DA98E6705C 31.11972; -97.90167 (Elev. 1092 ft) 09:11:46 up 5 days, 18:00, 1 user, load average: 0.56, 0.23, 0.24 Description: Ubuntu 16.04.2 LTS, kernel 4.4.0-64-generic
Attachment:
signature.asc
Description: This is a digitally signed message part