Tracker is just unusable with Jaunty/ext4 from an upgrade. I removed it, and installed beagle : indexing is fine, longer but system doesn't slow down like tracker... and it doesn't hang.
I agree with the last post, this bug have to be fixed before the final release. On Wed, Apr 22, 2009 at 2:54 AM, Ciprian Enache <ciprian.ena...@gmail.com>wrote: > The importance of this bug should be very high - it will impact many > users that have above a few GBs of indexable data. It might even have > "blocker" potential. Currently I'm learning to live without indexing > until this bug is fixed. > > A possible workaround [needs the tracker-utils package - sudo aptitude > install tracker-utils] is to reset databases and clear caches: > tracker-processes -r > > If the workaround is ineffective you might want to uninstall the package: > sudo aptitude remove tracker > > -- > 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: > > na...@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? > -- Tracker index corruption (was Tracker does not stop indexing) https://bugs.launchpad.net/bugs/346912 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
