Comment 71 for bug 346912

Revision history for this message
Alex Cozac (alex-cozac) wrote : Re: [Bug 346912] Re: Tracker index corruption (was Tracker does not stop indexing)

Hi Mike.

Thanks so much...next week my Computer "Guru" programmer Son will visit
us...so he will repair this bug I hope!.

Thanks again i will inform you...the finally results!.

Cheers,

Alex!

On Fri, May 22, 2009 at 10:00 AM, Mr. Mike <email address hidden> wrote:

> I'd like to add that, for me:
>
> tracker-processes -r
> [unsure if required - removed 2 remaining files in ~/.cache/tracker]
> /usr/lib/tracker/trackerd &
> tracker-applet &
>
> Seems to have tracker back and working again. I could have logged out
> and back in I guess after the first 2 lines, but the whole purpose of
> linux is stability and not having to do all that windows-like stuff :)
>
> Tracker seems happy once again.
>
> --
> Tracker index corruption (was Tracker does not stop indexing)
> https://bugs.launchpad.net/bugs/346912
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Meta-tracker: New
> Status in “tracker” source package in Ubuntu: Triaged
> Status in tracker in Ubuntu Jaunty: Triaged
>
> Bug description:
> I recently realized that tracker does not always give me the search results
> I expected, meaning that it does not find documents containing certain
> words. A quick look through the indexer preferences, I doubled the "maximal
> amount of text to index" and "maximum number of unique words to index".
> After doing so, the tracker does not stop indexing. The information message
> when I hover over the tracker icons says:
>
> Tracker: Indexing
> Done: 883 of 22296
> Estimated: 33 minutes ...
> Elapsed: 01 minute ...
>
> This message hasn't changed for about a day, and the indexing continues.
> One of my log files is continuously flooded with the following messages:
>
> nasko@serre:~/.local/share/tracker$ tail -n20 tracker-indexer.log
>
> 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'previous':
> with fatal error
>
> 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'troubl':
> with fatal error
>
> 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word
> 'preprocessor': with fatal error
>
> 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word
> 'ac_abs_top_builddir': with fatal error
>
> 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'detail':
> with fatal error
>
> 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'call':
> with fatal error
>
> 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'paramet':
> with fatal error
>
> 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'offshoot':
> with fatal error
>
> 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'with_gcc':
> with fatal error
>
> 22 Mar 2009, 15:11:17: Tracker-Warning **: Could not store word 'honor':
> with fatal error
>
>
> I would like to have tracker index my files more fully, and yet have it do
> that in a normal manner. Is there a way to prevent this problem?
>