Re: [Tracker] tracker-miner-fs stuck Initializing

[Martyn Russell <martyn lanedo com>]

On 29/10/13 11:03, Brian J. Murrell wrote:
> On 10/29/2013 06:29 AM, Carlos Garnacho wrote:
> > Hi Brian,
>
> Hi Carlos.
>
> > Could you terminate it and run your own
> > with /usr/lib/tracker/tracker-miner-fs -v 3? That should give some more
> > information about what's going on there.
>
> Seems to have stopped with:
>
> (tracker-miner-fs:14538): Tracker-CRITICAL **: Could not initialize
> currently active mount points:
> GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: column
> nie:url is not unique (strerror of errno (not necessarily related): No
> such file or directory)
> (tracker-miner-fs:14538): Tracker-CRITICAL **: Could not set mount point
> in database 'urn:nepomuk:datasource:448659eed398985de3972d3a72c8ac8d',
> GDBus.Error:org.freedesktop.Tracker1.SparqlError.Internal: column
> nie:url is not unique (strerror of errno (not necessarily related): No
> such file or directory)
>
> > As a last choice I'd recommend to dump previous info and retrigger
> > indexing with tracker-control -rs, but would be interesting to know
> > what's going on there.
>
> Yeah, I have kept that in reserve.  If it has to be done, I guess I will
> but I'd like to avoid it if i can, as I am sure you'd imagine.

Thank you for reporting this here. I think this issue is related to 
mounted GVFS locations.

I've noticed something strange happening with mount points and starting 
tracker. Unmounting them seemed to fix this "blockage" you talk of.

I've not had time to look into it myself but the errors you report above 
give us much more insight as to what's causing this.

I thought there was a bug reported about this, but I couldn't find it/one.

It's quite severe though and should be fixed!

--
Regards,
Martyn

Founder & Director @ Lanedo GmbH.
http://www.linkedin.com/in/martynrussell