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

[Chris]

On Sun, 2017-03-05 at 16:57 +0100, Philip Van Hoof wrote:
> On Tue, 2017-02-28 at 08:33 -0600, Chris wrote:
> > 
> > On Tue, 2017-02-28 at 09:10 +0100, Jean-Christophe Baptiste wrote:
> 
> Hello Chris,
> 
> You asked a question about how to do something a Tracker developer
> (more
> specifically the Debian packager) asked you to do for debugging
> purposes. Presumably to find out if there are any integration issues.
> 
>   Don't worry about asking such questions.
> 
> Jean-Christophe Baptiste has no authority on defining what are and
> what
> aren't permitted questions.
> 
> Kind regards,
> 
> Philip
> 
Thanks for the reply Philip, I never did figure out how to monitor it
in real time however I did file a bug on Gnome Bugzilla https://bugzill
a.gnome.org/show_bug.cgi?id=779342 a patch has been written I'm just
waiting now for Ubuntu to pick it up and publish.

Chris

> > 
> > > 
> > > > 
> > > > > 
> > > > > > 
> > > > > > chris@localhost:~$ ls -l /run/user/1000/dconf
> > > > > > total 4
> > > > > > -rw--- 1 chris chris 2 Feb 27 16:06 user
> > > > > 
> > > > > You need to check the permissions when this actually happens.
> > > > > 
> > > > > As soon as you stop the root X process, the permissions are
> > > > > typically
> > > > > restored.
> > > > > 
> > > > > 
> > > > What's the best way to monitor that?
> > > 
> > > Seriously, this is not a sysadmin mailing list. There are plenty
> > > of
> > > solutions on Google.
> > > 
> > Sorry, I'm not a sysdamin, I'm a 68yr old home user who is trying
> > to
> > get this figured out without much success. I did try Google before
> > asking but maybe I didn't use the correct search terms. I'll try
> > and
> > think up some better ones to use. Apologies for all the noise on
> > the
> > list.
> > 
> > ___
> > tracker-list mailing list
> > tracker-list@gnome.org
> > https://mail.gnome.org/mailman/listinfo/tracker-list
> 
-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
11:40:45 up 2 days, 20:09, 2 users, load average: 0.27, 0.17, 0.12
Description:Ubuntu 16.04.2 LTS, kernel 4.4.0-65-generic

signature.asc
Description: This is a digitally signed message part
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[Philip Van Hoof]

On Tue, 2017-02-28 at 08:33 -0600, Chris wrote:
> On Tue, 2017-02-28 at 09:10 +0100, Jean-Christophe Baptiste wrote:

Hello Chris,

You asked a question about how to do something a Tracker developer (more
specifically the Debian packager) asked you to do for debugging
purposes. Presumably to find out if there are any integration issues.

Don't worry about asking such questions.

Jean-Christophe Baptiste has no authority on defining what are and what
aren't permitted questions.

Kind regards,

Philip


> > > > > chris@localhost:~$ ls -l /run/user/1000/dconf
> > > > > total 4
> > > > > -rw--- 1 chris chris 2 Feb 27 16:06 user
> > > > 
> > > > You need to check the permissions when this actually happens.
> > > > 
> > > > As soon as you stop the root X process, the permissions are
> > > > typically
> > > > restored.
> > > > 
> > > > 
> > > What's the best way to monitor that?
> > 
> > Seriously, this is not a sysadmin mailing list. There are plenty of
> > solutions on Google.
> > 
> Sorry, I'm not a sysdamin, I'm a 68yr old home user who is trying to
> get this figured out without much success. I did try Google before
> asking but maybe I didn't use the correct search terms. I'll try and
> think up some better ones to use. Apologies for all the noise on the
> list.
> 
> ___
> tracker-list mailing list
> tracker-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/tracker-list



signature.asc
Description: This is a digitally signed message part
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[Chris]

On Tue, 2017-02-28 at 16:49 +0100, Carlos Garnacho wrote:
> Hi Chris,
> 
> On Tue, Feb 28, 2017 at 3:50 PM, Chris 
> wrote:
> > 
> > On Tue, 2017-02-28 at 11:23 +0100, Carlos Garnacho wrote:
> > > 
> > > Hi,
> > > 
> > > On Mon, Feb 27, 2017 at 6:52 PM, Chris 
> > > wrote:
> > > > 
> > > > 
> > > > 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.
> > > > Feb 27 11:46:42 localhost tracker-extract.desktop[3603]:
> > > > message
> > > > repeated 2 times: [ (tracker-extract:3603): dconf-CRITICAL **:
> > > > unable
> > > > to create file '/run/user/1000/dconf/user': Permission
> > > > denied.  dconf
> > > > will not work properly.]
> > > 
> > > I've noticed this warning across reported logs since the
> > > tracker-extract process was sandboxed. I suspect this is related
> > > to a
> > > sandboxed thread accessing gsettings, although it's most clearly
> > > not
> > > tracker itself, since all tracker-extract settings are read on
> > > startup
> > > and in-memory representation is accessible readonly to the
> > > extractor
> > > threads.
> > > 
> > > So this could be some tracker module that is trying to poke
> > > GSettings
> > > underneath, but I'm entirely unclear which. If anyone can get me
> > > backtrace of that specific warning (eg. setting up
> > > G_DEBUG=fatal-criticals in tracker-extract environment), that'd
> > > be
> > > appreciated.
> > > 
> > > That said, the warning should be harmless, at least if I'm right.
> > > 
> > > Cheers,
> > >   Carlos
> > > 
> > 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 2
> > minutes. I find that very hard to believe that could happen
> > especially
> > since the only process I have that continuously wakes every 2
> > minutes
> > if fetchmail and it's not an X process. I can open Gnome terminal
> > and
> > see that the timestamp -rw--- 1 chris chris 2 Feb 28 08:42 user
> > is
> > the same as when I go to check it with the ls -l command. IOW I'm
> > beginning to agree with you now that I don't think the permissions
> > are
> > being changed but tracker thinks they are. Does that sound about
> > right?
> 
> That is precisely what I think is happening. Inside the sandboxed
> bits, open() with write permissions is disallowed altogether, I think
> something is attempting to read settings inside the sandbox which in
> turn tries to open that file with readwrite permission. I've only
> seen
> this warning recently in recent bug reports, and always tied to
> tracker-extract.
> 
> On second read of gsettings/dconf code, it seems possible that file
> descriptors are reloaded behind our back, so it sounds plausible that
> it is tracker-extract after all, I'm doing a patch that I think
> should
> fix these warnings.
> 
> > 
> > 
> > Since I'm retired and don't have much else to do except tend to my
> > plants and go to doctors appointments at the VA I'll give setting
> > up
> > the backtrace you need a try if you can point me to a good how-to.
> 
> I'll try to make the patch available upstream asap, so hopefully
> Ubuntu will pick it up soon. If you anyway want to get into this
> trouble :), here's some steps:
> 
> 1) you need gdb installed, and hopefully tracker debuginfo packages
> so
> the backtrace has more sense
> 2) in a terminal do: tracker daemon -t
> 3) in another terminal do:
>    G_DEBUG=fatal-criticals gdb /usr/lib/tracker/tracker-extract
> 4) in the gdb prompt, do 'r' (shortcut for "run"), tracker-extract
> will run as usual
> 5) back in the first terminal, do: tracker daemon -s
> 6) get on with your normal activity
> 7) when the warning is hit (assuming it's the first one you'll get),
> gdb will be back to its prompt, you can do "t a a bt" to get the
> backtrace for all threads (what I ask for), or you can tell it to
> continue with 'c'.
> 
> Please do file a bug to bugzilla.gnome.org with this information.
> 
> Cheers,
>   Carlos
> 
Easy Carlos, at least I got output that made sense :) I had already
filed a bug last night - https://bugzilla.gnome.org/show_bug.cgi?id=779
342 and added the backtrace output as an attachment to it.

Chris

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
11:11:36 up 5 days, 20:00, 1 user, load average: 0.07, 0.20, 0.29
Description:Ubuntu 16.04.2 LTS, kernel 4.4.0-64-generic

signature.asc
Description: This is a digitally signed message part
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[Carlos Garnacho]

Hi Chris,

On Tue, Feb 28, 2017 at 3:50 PM, Chris  wrote:
> On Tue, 2017-02-28 at 11:23 +0100, Carlos Garnacho wrote:
>> Hi,
>>
>> On Mon, Feb 27, 2017 at 6:52 PM, Chris 
>> wrote:
>> >
>> > 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.
>> > Feb 27 11:46:42 localhost tracker-extract.desktop[3603]: message
>> > repeated 2 times: [ (tracker-extract:3603): dconf-CRITICAL **:
>> > unable
>> > to create file '/run/user/1000/dconf/user': Permission
>> > denied.  dconf
>> > will not work properly.]
>>
>> I've noticed this warning across reported logs since the
>> tracker-extract process was sandboxed. I suspect this is related to a
>> sandboxed thread accessing gsettings, although it's most clearly not
>> tracker itself, since all tracker-extract settings are read on
>> startup
>> and in-memory representation is accessible readonly to the extractor
>> threads.
>>
>> So this could be some tracker module that is trying to poke GSettings
>> underneath, but I'm entirely unclear which. If anyone can get me
>> backtrace of that specific warning (eg. setting up
>> G_DEBUG=fatal-criticals in tracker-extract environment), that'd be
>> appreciated.
>>
>> That said, the warning should be harmless, at least if I'm right.
>>
>> Cheers,
>>   Carlos
>>
> 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 2
> minutes. I find that very hard to believe that could happen especially
> since the only process I have that continuously wakes every 2 minutes
> if fetchmail and it's not an X process. I can open Gnome terminal and
> see that the timestamp -rw--- 1 chris chris 2 Feb 28 08:42 user is
> the same as when I go to check it with the ls -l command. IOW I'm
> beginning to agree with you now that I don't think the permissions are
> being changed but tracker thinks they are. Does that sound about
> right?

That is precisely what I think is happening. Inside the sandboxed
bits, open() with write permissions is disallowed altogether, I think
something is attempting to read settings inside the sandbox which in
turn tries to open that file with readwrite permission. I've only seen
this warning recently in recent bug reports, and always tied to
tracker-extract.

On second read of gsettings/dconf code, it seems possible that file
descriptors are reloaded behind our back, so it sounds plausible that
it is tracker-extract after all, I'm doing a patch that I think should
fix these warnings.

>
> Since I'm retired and don't have much else to do except tend to my
> plants and go to doctors appointments at the VA I'll give setting up
> the backtrace you need a try if you can point me to a good how-to.

I'll try to make the patch available upstream asap, so hopefully
Ubuntu will pick it up soon. If you anyway want to get into this
trouble :), here's some steps:

1) you need gdb installed, and hopefully tracker debuginfo packages so
the backtrace has more sense
2) in a terminal do: tracker daemon -t
3) in another terminal do:
   G_DEBUG=fatal-criticals gdb /usr/lib/tracker/tracker-extract
4) in the gdb prompt, do 'r' (shortcut for "run"), tracker-extract
will run as usual
5) back in the first terminal, do: tracker daemon -s
6) get on with your normal activity
7) when the warning is hit (assuming it's the first one you'll get),
gdb will be back to its prompt, you can do "t a a bt" to get the
backtrace for all threads (what I ask for), or you can tell it to
continue with 'c'.

Please do file a bug to bugzilla.gnome.org with this information.

Cheers,
  Carlos
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[Chris]

On Tue, 2017-02-28 at 15:59 +0100, Michael Biebl wrote:
> 2017-02-28 15:50 GMT+01:00 Chris :
> > 
> > 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 2
> 
> 
> There 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 "
> 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

signature.asc
Description: This is a digitally signed message part
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[Michael Biebl]

2017-02-28 15:50 GMT+01:00 Chris :
> 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 2


There 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 "
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.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[Chris]

On Tue, 2017-02-28 at 11:23 +0100, Carlos Garnacho wrote:
> Hi,
> 
> On Mon, Feb 27, 2017 at 6:52 PM, Chris 
> wrote:
> > 
> > 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.
> > Feb 27 11:46:42 localhost tracker-extract.desktop[3603]: message
> > repeated 2 times: [ (tracker-extract:3603): dconf-CRITICAL **:
> > unable
> > to create file '/run/user/1000/dconf/user': Permission
> > denied.  dconf
> > will not work properly.]
> 
> I've noticed this warning across reported logs since the
> tracker-extract process was sandboxed. I suspect this is related to a
> sandboxed thread accessing gsettings, although it's most clearly not
> tracker itself, since all tracker-extract settings are read on
> startup
> and in-memory representation is accessible readonly to the extractor
> threads.
> 
> So this could be some tracker module that is trying to poke GSettings
> underneath, but I'm entirely unclear which. If anyone can get me
> backtrace of that specific warning (eg. setting up
> G_DEBUG=fatal-criticals in tracker-extract environment), that'd be
> appreciated.
> 
> That said, the warning should be harmless, at least if I'm right.
> 
> Cheers,
>   Carlos
> 
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 2
minutes. I find that very hard to believe that could happen especially
since the only process I have that continuously wakes every 2 minutes
if fetchmail and it's not an X process. I can open Gnome terminal and
see that the timestamp -rw--- 1 chris chris 2 Feb 28 08:42 user is
the same as when I go to check it with the ls -l command. IOW I'm
beginning to agree with you now that I don't think the permissions are
being changed but tracker thinks they are. Does that sound about
right? 

Since I'm retired and don't have much else to do except tend to my
plants and go to doctors appointments at the VA I'll give setting up
the backtrace you need a try if you can point me to a good how-to. 

Chris

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
08:34:26 up 5 days, 17:22, 1 user, load average: 0.47, 0.33, 0.37
Description:Ubuntu 16.04.2 LTS, kernel 4.4.0-64-generic

signature.asc
Description: This is a digitally signed message part
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[Chris]

On Tue, 2017-02-28 at 09:10 +0100, Jean-Christophe Baptiste wrote:
> Le 27/02/2017 à 23:35, Chris a écrit :
> > 
> > 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 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 16:06 user
> > > 
> > > You need to check the permissions when this actually happens.
> > > 
> > > As soon as you stop the root X process, the permissions are
> > > typically
> > > restored.
> > > 
> > > 
> > What's the best way to monitor that?
> 
> Seriously, this is not a sysadmin mailing list. There are plenty of
> solutions on Google.
> 
Sorry, I'm not a sysdamin, I'm a 68yr old home user who is trying to
get this figured out without much success. I did try Google before
asking but maybe I didn't use the correct search terms. I'll try and
think up some better ones to use. Apologies for all the noise on the
list.

-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
08:31:17 up 5 days, 17:19, 1 user, load average: 0.32, 0.32, 0.39
Description:Ubuntu 16.04.2 LTS, kernel 4.4.0-64-generic

signature.asc
Description: This is a digitally signed message part
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[Carlos Garnacho]

Hi,

On Mon, Feb 27, 2017 at 6:52 PM, Chris  wrote:
> 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.
> Feb 27 11:46:42 localhost tracker-extract.desktop[3603]: message
> repeated 2 times: [ (tracker-extract:3603): dconf-CRITICAL **: unable
> to create file '/run/user/1000/dconf/user': Permission denied.  dconf
> will not work properly.]

I've noticed this warning across reported logs since the
tracker-extract process was sandboxed. I suspect this is related to a
sandboxed thread accessing gsettings, although it's most clearly not
tracker itself, since all tracker-extract settings are read on startup
and in-memory representation is accessible readonly to the extractor
threads.

So this could be some tracker module that is trying to poke GSettings
underneath, but I'm entirely unclear which. If anyone can get me
backtrace of that specific warning (eg. setting up
G_DEBUG=fatal-criticals in tracker-extract environment), that'd be
appreciated.

That said, the warning should be harmless, at least if I'm right.

Cheers,
  Carlos
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[Jean-Christophe Baptiste]

Le 27/02/2017 à 23:35, Chris a écrit :
> 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 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 16:06 user
>>
>> You need to check the permissions when this actually happens.
>>
>> As soon as you stop the root X process, the permissions are typically
>> restored.
>>
>>
> What's the best way to monitor that?

Seriously, this is not a sysadmin mailing list. There are plenty of
solutions on Google.

> 
> 
> 
> 
> ___
> tracker-list mailing list
> tracker-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/tracker-list
> 


-- 
JCB



signature.asc
Description: OpenPGP digital signature
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[Chris]

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 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 16:06 user
> > 
> > You need to check the permissions when this actually happens.
> > 
> > As soon as you stop the root X process, the permissions are
> > typically
> > restored.
> > 
> > 
> What's the best way to monitor that?
> 
I probably mentioned this but this goes on 24/7, every two minutes. I
can't narrow it down to any process that is starting and stopping. The
only process I can say for sure that starts and stops every two minutes
is fetchmail when it polls my main mail account and I'm pretty sure
that that's not a root X process.

> ___
> tracker-list mailing list
> tracker-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/tracker-list
-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
16:48:15 up 5 days, 1:36, 1 user, load average: 0.41, 0.35, 0.27
Description:Ubuntu 16.04.2 LTS, kernel 4.4.0-64-generic

signature.asc
Description: This is a digitally signed message part
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[Chris]

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 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 16:06 user
> 
> You need to check the permissions when this actually happens.
> 
> As soon as you stop the root X process, the permissions are typically
> restored.
> 
> 
What's the best way to monitor that?


-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
16:26:07 up 5 days, 1:14, 1 user, load average: 0.42, 0.30, 0.22
Description:Ubuntu 16.04.2 LTS, kernel 4.4.0-64-generic

signature.asc
Description: This is a digitally signed message part
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[Michael Biebl]

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 /run/user/1000/dconf
> total 4
> -rw--- 1 chris chris 2 Feb 27 16:06 user

You need to check the permissions when this actually happens.

As soon as you stop the root X process, the permissions are typically restored.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[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 /run/user/1000/dconf
total 4
-rw--- 1 chris chris 2 Feb 27 16:06 user

chris@localhost:~$ ls -l /run/user/1000
total 16
-rw-rw-r-- 1 chris chris  60 Feb 22 15:13 dbus-session
drwx-- 2 chris chris  60 Feb 27 16:07 dconf
drwx--x--x 2 chris chris  60 Feb 22 15:13 gdm
drwx-- 3 chris chris  60 Feb 22 15:14 gnome-shell
dr-x-- 2 chris chris   0 Feb 22 15:14 gvfs
drwx-- 2 chris chris  40 Feb 22 17:42 gvfs-burn
drwx-- 2 chris chris 100 Feb 22 15:14 keyring
drwx-- 2 chris chris  80 Feb 22 15:14 pulse
drwx-- 3 chris chris  60 Feb 22 15:15 snap.wallpaperdownloader
drwxr-xr-x 2 chris chris  80 Feb 22 15:13 systemd
drwx-- 3 chris chris  60 Feb 22 15:13 upstart
-rw-r--r-- 1 chris chris   5 Feb 22 15:14 upstart-dbus-bridge.3095.pid
-rw-r--r-- 1 chris chris   5 Feb 22 15:14 upstart-file-bridge.3095.pid
-rw-r--r-- 1 chris chris   5 Feb 22 15:13 upstart-udev-bridge.3095.pid
> 
> 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 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.
> > Feb 27 11:46:42 localhost tracker-extract.desktop[3603]: message
> > repeated 2 times: [ (tracker-extract:3603): dconf-CRITICAL **:
> > unable
> > to create file '/run/user/1000/dconf/user': Permission
> > denied.  dconf
> > will not work properly.]
> > 
> > Is this a tracker bug or a dconf bug? I filed this bug report -
> > https:/
> > /bugs.launchpad.net/ubuntu/+source/dconf/+bug/1654406 on Ubuntu
> > Launchpad back in Jan, it's been confirmed however it appears as
> > though
> > they've assigned it to no one for a fix. If this is a dconf but I
> > apologize for the noise and maybe someone can let me know where I
> > can
> > go to see about getting it fixed.
> > 
> > Chris
> > 
> > --
> > Chris
> > KeyID 0xE372A7DA98E6705C
> > 31.11972; -97.90167 (Elev. 1092 ft)
> > 11:42:41 up 4 days, 20:31, 1 user, load average: 0.48, 0.17, 0.17
> > Description:Ubuntu 16.04.2 LTS, kernel 4.4.0-64-generic
> > ___
> > tracker-list mailing list
> > tracker-list@gnome.org
> > https://mail.gnome.org/mailman/listinfo/tracker-list
> > 
> 
> 
> 
-- 
Chris
KeyID 0xE372A7DA98E6705C
31.11972; -97.90167 (Elev. 1092 ft)
16:07:08 up 5 days, 55 min, 1 user, load average: 0.59, 0.30, 0.16
Description:Ubuntu 16.04.2 LTS, kernel 4.4.0-64-generic

signature.asc
Description: This is a digitally signed message part
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list

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

[Michael Biebl]

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 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.
> Feb 27 11:46:42 localhost tracker-extract.desktop[3603]: message
> repeated 2 times: [ (tracker-extract:3603): dconf-CRITICAL **: unable
> to create file '/run/user/1000/dconf/user': Permission denied.  dconf
> will not work properly.]
>
> Is this a tracker bug or a dconf bug? I filed this bug report - https:/
> /bugs.launchpad.net/ubuntu/+source/dconf/+bug/1654406 on Ubuntu
> Launchpad back in Jan, it's been confirmed however it appears as though
> they've assigned it to no one for a fix. If this is a dconf but I
> apologize for the noise and maybe someone can let me know where I can
> go to see about getting it fixed.
>
> Chris
>
> --
> Chris
> KeyID 0xE372A7DA98E6705C
> 31.11972; -97.90167 (Elev. 1092 ft)
> 11:42:41 up 4 days, 20:31, 1 user, load average: 0.48, 0.17, 0.17
> Description:Ubuntu 16.04.2 LTS, kernel 4.4.0-64-generic
> ___
> tracker-list mailing list
> tracker-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/tracker-list
>



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
___
tracker-list mailing list
tracker-list@gnome.org
https://mail.gnome.org/mailman/listinfo/tracker-list