GNOME Bugzilla – Bug 539296
crash in Deskbar:
Last modified: 2008-06-22 11:08:23 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mac4Lin_Icons_v0.4 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 (12 sec old) --------------------- (firefox-bin:11514): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (firefox-bin:11514): Gdk-CRITICAL **: gdk_screen_get_display: assertion `GDK_IS_SCREEN (screen)' failed (firefox-bin:11514): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (firefox-bin:11514): GLib-GObject-WARNING **: /home/oliver/Desktop/glib2.0-2.15.6/gobject/gsignal.c:2180: invalid unclassed object pointer for value type `GdkScreen' (firefox-bin:11514): Gdk-CRITICAL **: gdk_screen_get_display: assertion `GDK_IS_SCREEN (screen)' failed (firefox-bin:11514): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (firefox-bin:11514): GLib-GObject-WARNING **: /home/oliver/Desktop/glib2.0-2.15.6/gobject/gsignal.c:2180: invalid unclassed object pointer for value type `GdkScreen' (firefox-bin:11514): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 200938
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
if text.startswith(query):
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 475351 ***