GNOME Bugzilla – Bug 500384
crash in Deskbar: I was searching a word a...
Last modified: 2007-11-29 18:51:42 UTC
What were you doing when the application crashed? I was searching a word after I tried to configure the tracking tool so that it would also search in my windows hard disk. But I didn't really figure it out yet how to do. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors --------------------- ** (trackerd:5467): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:5467): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:5467): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:5467): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:5467): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:5467): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed checking for valid crashreport now checking for valid crashreport now checking for valid crashreport now checking for valid crashreport now -------------------------------------------------- Traceback (most recent call last):
+ Trace 180063
self._on_hit_added(query, container, qstring, qmax)
match = BeagleLiveMatch(result, category=cat_type, priority=self.get_priority())
display_name=basename(unescaped_uri)
mime = gnomevfs.get_mime_type(uri)
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 474131 ***