GNOME Bugzilla – Bug 486014
crash in Deskbar: Searched for help, and w...
Last modified: 2007-10-13 16:15:44 UTC
What were you doing when the application crashed? Searched for help, and was watching a flash video clip online. 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: 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 (517 sec old) --------------------- /usr/lib/python2.5/site-packages/AppInstall/AppInstall.py:1261: GtkWarning: gtk_tree_model_sort_sort: assertion `tree_model_sort->default_sort_func != NULL' failed item.applications.set_default_sort_func(None) (yelp:9663): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup. (yelp:9663): atk-bridge-WARNING **: IOR not set. (yelp:9663): atk-bridge-WARNING **: Could not locate registry Window manager warning: Window 0x2e02fc5 () sets an MWM hint indicating it isn't resizable, but sets min size 461 x 278 and max size 2147483647 x 2147483647; this doesn't make much sense. Window manager warning: Window 0x2e02fc5 () sets an MWM hint indicating it isn't resizable, but sets min size 461 x 278 and max size 2147483647 x 2147483647; this doesn't make much sense. (yelp:9663): Yelp-WARNING **: beagled not running, using basic search support. Window manager warning: last_focus_time (2485419832) is greater than comparison timestamp (2485419827). This most likely represents a buggy client sending inaccurate timestamps in messages such as _N Window manager warning: Log level 8: gtk_menu_shell_insert: assertion `GTK_IS_MENU_ITEM (child)' failed Window manager warning: Log level 8: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 169725
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):
Thank you for reporting this bug. It looks like this bug is the same as bug 472134
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 ***