GNOME Bugzilla – Bug 484104
crash in Deskbar: network manager opstarte...
Last modified: 2007-10-07 09:07:20 UTC
What were you doing when the application crashed? network manager opstarten Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Orange-LiNstaBlackPlastic 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 (36 sec old) --------------------- ** (trackerd:9724): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:9724): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:9724): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:9724): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:9724): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:9724): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:9724): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed ** (trackerd:9724): CRITICAL **: tracker_indexer_get_hits: assertion `query->words' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 168300
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):
*** Bug 484122 has been marked as a duplicate of this bug. ***
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 ***