Bug 489606

Can you please attached your trackerd log file (/var/log/trackerd.log).

Also if you can, please file this bug upstream (http://bugzilla.gnome.org/browse.cgi?product=tracker).

Excuse me, I think the trackerd log file can be found in ~/.local/share/tracker/trackerd.log .

There is such a file, but it's currently empty.  Would any of the other files in that directory be useful?

Have you also looked for /var/log/trackerd.log? You can try and kill any presently running trackerd instance ('killall -9 trackerd'); and then re-run trackerd manually with ('trackerd -v 3') ,i.e. with higher level of logging, and then check ~/.local/share/tracker/trackerd.log .

However, would please try the new 0.6.91 release, and see if it has already solved the issue. Rawhide build for the new release are available at;
http://koji.fedoraproject.org/koji/taskinfo?taskID=1240307

I have been running that version for a few days now, but it hasn't resolved the problem.  The system load is over 4 while the indexer is running, making it rather sluggish.

Here's what's in the log file:

20 Mar 2009, 19:24:46: GLib-GIO-Critical **: g_file_hash: assertion `G_IS_FILE (file)' failed

20 Mar 2009, 19:24:46: GLib-GIO-Critical **: g_file_hash: assertion `G_IS_FILE (file)' failed

20 Mar 2009, 19:24:46: GLib-GIO-Critical **: g_file_hash: assertion `G_IS_FILE (file)' failed

Have been running with the extra debug setting and after a while a notification bubble appears, saying "There was an error while performing indexing: Index corrupted".

It offers the option to "Reindex all contents".  I've tried that several times but after a few minutes the error bubble re-appears.

This is still happening with the latest version from today's Rawhide:

tracker-0.6.94-1.fc11.x86_64

I believe you're still running with Verbosity=3 in your tracker configuration file (~/.config/tracker/tracker.cfg). If so, have you noticed extra info in the tracker log (~/.local/share/tracker/) that might help resolve this.
I think tracker might be having problem with some file(s) on your computer.

What sort of thing should I be looking for in the log files?

(In reply to comment #9)
> What sort of thing should I be looking for in the log files?  

I think tracker might be choking on some particular file(s) on your computer. 

Maybe you should back-up your old tracker config and indexes (~/.config/tracker and ~/.local/share) and 'start afresh'. I can't reproduce this issue.

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

tracker-0.6.96-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/tracker-0.6.96-1.fc12

tracker-0.6.96-1.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/tracker-0.6.96-1.fc11

tracker-0.6.96-1.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update tracker'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2010-1522

tracker-0.6.96-1.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update tracker'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1525

tracker-0.6.96-2.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/tracker-0.6.96-2.fc12

tracker-0.6.96-2.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update tracker'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1615

This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.