Re: [Tracker] (tracker-extract:3603): dconf-CRITICAL

On Mon, 2017-02-27 at 16:35 -0600, Chris wrote: > On Mon, 2017-02-27 at 23:20 +0100, Michael Biebl wrote: > > > > 2017-02-27 23:09 GMT+01:00 Chris : > > > > > > > > > On Mon, 2017-02-27 at 19:31 +0100, Michael Biebl wrote: > > > > > > > > > > > > Can you check the

Re: [Tracker] (tracker-extract:3603): dconf-CRITICAL

On Mon, 2017-02-27 at 23:20 +0100, Michael Biebl wrote: > 2017-02-27 23:09 GMT+01:00 Chris : > > > > On Mon, 2017-02-27 at 19:31 +0100, Michael Biebl wrote: > > > > > > Can you check the permissions of /run/user/1000/dconf/user? My > > > guess > > > is that it is root

Re: [Tracker] (tracker-extract:3603): dconf-CRITICAL

2017-02-27 23:09 GMT+01:00 Chris : > On Mon, 2017-02-27 at 19:31 +0100, Michael Biebl wrote: >> Can you check the permissions of /run/user/1000/dconf/user? My guess >> is that it is root owned because you've started an X application as >> root. > > chris@localhost:~$ ls -l

Re: [Tracker] (tracker-extract:3603): dconf-CRITICAL

On Mon, 2017-02-27 at 19:31 +0100, Michael Biebl wrote: > Can you check the permissions of /run/user/1000/dconf/user? My guess > is that it is root owned because you've started an X application as > root. chris@localhost:~$ ls -l /run/user/1000/dconf total 4 -rw--- 1 chris chris 2 Feb 27

Re: [Tracker] (tracker-extract:3603): dconf-CRITICAL

Can you check the permissions of /run/user/1000/dconf/user? My guess is that it is root owned because you've started an X application as root. 2017-02-27 18:52 GMT+01:00 Chris : > The complete notation to my syslog that I'm seeing every two minutes > every hour, every day

[Tracker] (tracker-extract:3603): dconf-CRITICAL

The complete notation to my syslog that I'm seeing every two minutes every hour, every day is: Feb 27 11:44:33 localhost tracker-extract.desktop[3603]: (tracker- extract:3603): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.