GNOME Bugzilla – Bug 488726
crash in Deskbar: Added Deskbar to panel
Last modified: 2007-10-21 10:38:12 UTC
What were you doing when the application crashed? Added Deskbar to panel 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: Murrina Sunset Icon Theme: Gion 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 --------------------- (tilda:8076): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed (tilda:8076): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed Unable to open desktop file file:///home/jiri/Desktop/nautilus-home.desktop for panel launcher: No such file or directory (tilda:8076): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed (tilda:8076): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed ** (gnome-app-install:8271): 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) Unable to open desktop file file:///home/jiri/Desktop/nautilus-home.desktop for panel launcher: No such file or directory Unable to open desktop file file:///home/jiri/Desktop/nautilus-home.desktop for panel launcher: No such file or directory -------------------------------------------------- Traceback (most recent call last):
+ Trace 171776
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 ***