GNOME Bugzilla – Bug 506688
crash in Deskbar: sie gestartet
Last modified: 2008-01-02 11:23:38 UTC
What were you doing when the application crashed? sie gestartet Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-386 #1 Tue Dec 18 07:34:24 UTC 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 (26 sec old) --------------------- ** (trackerd:6049): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6049): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6049): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6049): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6049): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6049): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6049): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6049): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 183702
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
result += self._query_filefolder(query, True)
return [FileMatch(join(prefix, basename(completion)), "file://"+completion, priority=self.get_priority()) for completion in completions]
self.add_all_actions( get_actions_for_uri(absname) )
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 ***