GNOME Bugzilla – Bug 547176
crash in Deskbar:
Last modified: 2008-08-10 19:34:28 UTC
What were you doing when the application crashed? Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.3 2008-07-09 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Human-Clearlooks 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 (120 sec old) --------------------- ** Message: GetValue variable 2 (2) GCJ PLUGIN: thread 0x805f0e0: NP_GetMIMEDescription GCJ PLUGIN: thread 0x805f0e0: NP_GetMIMEDescription return GCJ PLUGIN: thread 0x805f0e0: NP_GetValue GCJ PLUGIN: thread 0x805f0e0: NP_GetValue: returning plugin name. GCJ PLUGIN: thread 0x805f0e0: NP_GetValue return GCJ PLUGIN: thread 0x805f0e0: NP_GetValue GCJ PLUGIN: thread 0x805f0e0: NP_GetValue: returning plugin description. GCJ PLUGIN: thread 0x805f0e0: NP_GetValue return (firefox:24252): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (<unknown>:6982): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == gdk_drawable_get_depth (window)' failed (<unknown>:6982): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == gdk_drawable_get_depth (window)' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 204945
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
posts = self._delicious.get_posts_by_tag(tag)
dom.unlink()
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 538425 ***