Corrupted tracker index causes persistent applet error popup

I have the same problem. If i choose "cancel" or "ok" button, the message come back. If I choose "reindex all contents", follow a message to confirm, and then for about an hour, the are no other messages. The problem is that if I don't choose "reindex all contents" button, the cpu/cpus works at 100% all over the time.

At some point the tracker was using a high amount of CPU. I killed one of the processes at the time.

Next time I logged in and it started, I got the message:

"Tracker
There was an error while performing indexing:

Index corrupted"

Hitting "OK" or "Cancel" or "Reindex all contents" brings the box back immediately.

tracker-indexer is running now using about half CPU, while trackerd is using the other half. The mouse over statistics on the tracker applet are not updating. I chose "pause all indexing" from the applet, but it's not affecting the processes or the popup error window.

The applet error message should check if the indexer is running and go away if it does.

While letting the tracker run after choosing 'Reindex all contents' the machine was relatively unusable. Firefox would gray out every couple of minutes, the mouse pointer was lagging. After letting the tracker run for a couple of hours, I came back to even my shell being grayed out and 'dbus-daemon' sharing half the CPU with 'tracker-indexer'. I had to hard power cycle the machine to get it back. A couple minutes after logging in the popup returned.

From the tracker applet, under indexer preferences, I unchecked "enable indexing" and chose apply. This lagged for about 30 seconds. In the interim I randomly clicked OK and Cancel for a while to pass the time. Then it told me it would need to restart trackerd, which it did, shortly thereafter (index delay?) the popup returned.

ps exposed that tracker-indexer was not a child of trackerd, so I killed it. Choosing to reindex started another indexer after I found the popup hidden behind other windows. The ok/cancel/reindex popup continued until I killed tracker-applet.

the dbus-daemon and tracker-indexer are still both pretty cpu heavy, but I'm going to let them keep running and the system seems mostly usable at the moment. If the index was corrupted, it'd be super nice if I 'delete it and stop telling me about this' was an option.

Exact same problem here. I tried stopping tracker and removing all the contents of the ~/.local/share/tracker/ directory and restarted.

But some moments later, I started to get the same pop ups as well.

Some logs:

$ tail .local/share/tracker/trackerd.log

18 Apr 2009, 09:14:35: Tracker-Warning **: Error loading query:'sqlite-fulltext.sql' #0, Cannot use virtual tables in shared-cache mode

18 Apr 2009, 09:14:35: Tracker-Warning **: Error loading query:'sqlite-fulltext.sql' #0, Cannot use virtual tables in shared-cache mode

(only these 2 lines there)

$ tail .local/share/tracker/tracker-indexer.log

18 Apr 2009, 09:36:37: Tracker-Warning **: Could not store word '04': with fatal error

18 Apr 2009, 09:36:37: Tracker-Warning **: Could not store word '04': with fatal error

(this error line is repeated endlessly and the error log file keeps getting recycled after it gets to ~10M)

Ops, forgot to mention, the issue started immediately after I upgraded to 9.04 beta.

I can confirm this bug. After upgrading to 9.04 RC 64bit, I can't get rid of this: (see attachment)

Same bug here. It's pretty disruptive.

After upgrading to 9.04 RC 64bit i get the same problem. Tracker uses 100% of CPU after giving me the index corrupted pop up. Temporarily stopped it by killing both trackerd and tracker-indexer. Confirming bug.

Same issue here. I just paused it. Hopefully will be a fix on the final release :-)

Also after upgrade from Intrpid to Jaunty, tracker problems including unstoppable message bus pop-up, firefox freezes and high cpu load. I already tried emptying the cache but still this result.

I'm in Jaunty, i've the same bug :(

I'm on Jaunty 9.04 RC and I have the same problem!

This Bug is quite annoying, as suggested i always have to kill both trackerd and tracker-indexer processes

Same issue - any one know a fix yet?

Similar here. Updated from 8.10 to 9.04 RC, and it seems as if the index likes to corrupt itself. It has corrupted 4 times in 2 hours.

I have the same problem my /home/user/.local/share/tracker/tracker-indexer.log shows ALOT of this:

21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error
21 Apr 2009, 09:33:34: Tracker-Warning **: Could not store word 'pst': with fatal error

I can confirm the bug cannot be solved by reindexing, only by removing the contents of ~/.cache/tracker, and of ~./.local/share/tracker/data. After reindexing then, everything is fine (I'm using version 0.6.93-0ubuntu1).

Maybe a more radical solution should be used by Tracker when the DB is corrupt, especially to help people that are upgrading from previous Jaunty states.

Ran into the same problem. Following jonaz__ solution, with the exception that I killed the trackerd and tracker-indexer processes, deleted the contents of ~/.cache/tracker and ~/.local/share/tracker/data then logged out, and logged back in. Tracker indexer posted a notification that it was starting up.

Suspect that the tracker from 8.10 and the version of tracker from 9.04 are using some of the same files, but may be using them slightly differently. Alternatively an error under 8.10 may have been silently ignored that is generating the dialog under the 9.04 rc code. Possibly debugging is still enabled? I have not looked at the code though, so I don't know if that is the right area to point at.

One 'fix' would be to have the installer discard the contents of those files as history, under the assumption that the new release will generate a new/clean index. I would suggest that a validation on the data happen though as I had different results on another machine. My primary desktop had no problem with the update. It's my laptop which encountered the issue.

Started happening to me after the RC update.

It is very disruptive. You either have to end the process or hit "Re-index" about 20 times before it will go away.

Also having the same issue....killing the tracker app just restarts it and in a few minutes it comes back up with a message about a corrupt index with multiple confirm and yes/no dialogues.

I can confirm this bug also updating from 8.10 to the officially released 9.04, which is a pity.

Can confirm this too, 64 bit as well as 32 bit. Just upgraded to jaunty, so it is the official release.

/home/user/.local/share/tracker/tracker-indexer.log is completely filled up with the following lines (85904 lines in total):

24 apr 2009, 14:33:58: Tracker-Warning **: Could not store word '4': with fatal error

24 apr 2009, 14:33:58: Tracker-Warning **: Could not store word '4': with fatal error

24 apr 2009, 14:33:58: Tracker-Warning **: Could not store word '4': with fatal error

24 apr 2009, 14:33:58: Tracker-Warning **: Could not store word '4': with fatal error

(filling this log with these sentences is by the way not stopped by stopping the applet, it just continues)
It looks like that something is changed in the database setup that is not covered by the update process
Deleting ~/.local/share/tracker and ~/.cache/tracker and /tmp/tracker-user did not fix the job. You had to logout and login again.

Same problem for me (64bit upgraded last night from 8.10 to 9.04)

To solve this problem I did as jonaz__ did. I killed the trackerd and tracker-indexer, and then deleted the contents of ~/.cache/tracker, and of ~./.local/share/tracker/data. After a reboot, I was good, haven't got the error message since I did this 4 days ago.

After experiencing this bug, my system drops to a crawl, it becomes basically unusable.

Since it also seems to be hitting a lot of people, should the importance be bumped to "critical"?

setting Importance to high. This seems to hit a lot of people.

I have also experienced this bug. By following this advice from jonaz/Rusty, I haven't seen the error message since:

"Ran into the same problem. Following jonaz__ solution, with the exception that I killed the trackerd and tracker-indexer processes, deleted the contents of ~/.cache/tracker and ~/.local/share/tracker/data then logged out, and logged back in. Tracker indexer posted a notification that it was starting up." https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/361560/comments/18

This worth for an SRU since it's affecting a good quantity of users. Approving the nomination there, thanks all.

I'm getting this too after updating from Intrepid to Jaunty. Please let me know if I can give any help.

Found a workaround/fix that's more user friendly:

sudo apt-get install tracker-utils
tracker-processes -r # --hard-reset

Then I logged out and back in so the processes that I had previously killed by hand would restart in a normal fashion.

Note that this probably gets rid of data that would be useful in finding a fix for others, which is sad.

I'm marking this a duplicate of bug #346912, there's much more developer and packaging discussion there, it's an earlier bug report, and also link to an upstream bug report [1].

[1] http://bugzilla.gnome.org/show_bug.cgi?id=577193

this is *very* annoying, i'm having the same problem. cancel and re-indexing doesn't even help.

I'm in Jaunty, i've the same bug :(
Re-indexing or clearing of tracker folders in home directory doesn't even help.

Hello to all of you!

My Son now arrange this problem in a very simpler way...HE DISABLE the
"Tracking Index"...so as for my needs is 100% completely NOT necessary at
all!.

Good luck.

Alex!

On Mon, Jun 1, 2009 at 7:06 PM, VladimirCZ <email address hidden> wrote:

> *** This bug is a duplicate of bug 346912 ***
> https://bugs.launchpad.net/bugs/346912
>
> I'm in Jaunty, i've the same bug :(
> Re-indexing or clearing of tracker folders in home directory doesn't even
> help.
>
> --
> Corrupted tracker index causes persistent applet error popup
> https://bugs.launchpad.net/bugs/361560
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (via bug 346912).
>
> Status in “tracker” source package in Ubuntu: Confirmed
> Status in tracker in Ubuntu Jaunty: Triaged
>
> Bug description:
> Binary package hint: gnome-session
>
>
> a Lot of messages form Tracker occur
>
> Message : There was an error while performing indexing : Index corrupted.
>
> There are three button on this dialog box : Reindex all contents, cancel,
> validate.
> Any button I pressed the message comeback...
> I have to stop the the tracker-indexer in Monitor-system to stop all
> messages.
>
> Best regards
>

received an upgrade to tracker yesterday, installed and all is well. guess
I can be unsubscribed from this bug.. thanks

On Sun, Jun 7, 2009 at 4:35 AM, Alex Cozac <email address hidden> wrote:

> *** This bug is a duplicate of bug 346912 ***
> https://bugs.launchpad.net/bugs/346912
>
>
>

--
Bob Davenport
ubuntu 9.04 Juanty Jackalope
I don't do windows anymore

Hello to all of you!

Really can't estimate HOW IMPORTANT...is such "Tracker Index Issue"???. My
Com puter expert Son...simply "Disable"...the "Tracker Index"...now all is
working well!.

Peace,

Alex!

On Sun, Jun 7, 2009 at 2:41 PM, greyebeard8550 <email address hidden> wrote:

> *** This bug is a duplicate of bug 346912 ***
> https://bugs.launchpad.net/bugs/346912
>
> received an upgrade to tracker yesterday, installed and all is well. guess
> I can be unsubscribed from this bug.. thanks
>
> On Sun, Jun 7, 2009 at 4:35 AM, Alex Cozac <email address hidden> wrote:
>
> > *** This bug is a duplicate of bug 346912 ***
> > https://bugs.launchpad.net/bugs/346912
> >
> >
> >
>
>
> --
> Bob Davenport
> ubuntu 9.04 Juanty Jackalope
> I don't do windows anymore
>
> --
> Corrupted tracker index causes persistent applet error popup
> https://bugs.launchpad.net/bugs/361560
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (via bug 346912).
>
> Status in “tracker” source package in Ubuntu: Confirmed
> Status in tracker in Ubuntu Jaunty: Triaged
>
> Bug description:
> Binary package hint: gnome-session
>
>
> a Lot of messages form Tracker occur
>
> Message : There was an error while performing indexing : Index corrupted.
>
> There are three button on this dialog box : Reindex all contents, cancel,
> validate.
> Any button I pressed the message comeback...
> I have to stop the the tracker-indexer in Monitor-system to stop all
> messages.
>
> Best regards
>

Nice "solution" Alex, thanks for posting it yesterday and, again, today.

Now you can also turn off the computer and not only tracker index but all computer related problems will be "solved" ;)

dan, please stay polite when disagreeing upon what is a clean fix and the importance thereof. surely alex' "solution" hardly is one, but it does the trick in his case -- and he is happy about it.

further technical discussion should be continued at bug #346912 because this bug is marked as duplicate thereof.