GNOME Bugzilla – Bug 491929
crash in Deskbar: I've just configured it ...
Last modified: 2007-10-31 02:30:18 UTC
What were you doing when the application crashed? I've just configured it to search in yahoo, and searched for "open arena" which it had found successfuly 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 (194 sec old) --------------------- ** (trackerd:6172): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6172): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6172): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6172): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6172): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6172): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6172): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:6172): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 174062
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()
raise socket.error, msg
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 472134 ***