GNOME Bugzilla – Bug 487204
crash in Deskbar: keine ahnung
Last modified: 2007-10-16 21:27:15 UTC
What were you doing when the application crashed? keine ahnung 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: Soffice 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 (42 sec old) --------------------- (tracker-search-tool:3802): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 128 (tracker-search-tool:3802): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 128 (tracker-search-tool:3802): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 128 (tracker-search-tool:3802): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 128 (tracker-search-tool:3802): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 82 ** (gnome-app-install:3810): WARNING **: return value of custom widget handler was not a GtkWidget /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) (tracker-search-tool:3867): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -7 and height 110 -------------------------------------------------- Traceback (most recent call last):
+ Trace 170604
self._history.load()
saved_history = cPickle.load(file(HISTORY_FILE))
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 474179 ***