GNOME Bugzilla – Bug 485836
crash in Deskbar: Typed in "ccsm" and pres...
Last modified: 2007-10-12 10:25:32 UTC
What were you doing when the application crashed? Typed in "ccsm" and pressed enter, possibly before it finished searching for results. 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 Wed Oct 10 06:00:47 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Tangerine 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:6435): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6435): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6435): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6435): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6435): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6435): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6435): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6435): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 169580
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
'results': 15}), proxies=get_proxy())
return opener.open(url)
return getattr(self, name)(url)
h.endheaders()
self._send_output()
self.send(msg)
self.connect()
socket.SOCK_STREAM):
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 482379 ***