GNOME Bugzilla – Bug 495129
crash in Deskbar:
Last modified: 2007-11-09 11:29:42 UTC
What were you doing when the application crashed? 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: Truth Icon Theme: micro 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 (20 sec old) --------------------- /usr/lib/awn/applets/BlingSwitcher/PySwitcher.py:57: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed self.ObjSwitcher.DrawSwitcher(applet) /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format /usr/lib/awn/applets/BlingSwitcher/PySwitcher.py:60: Warning: g_object_get_qdata: assertion `G_IS_OBJECT (object)' failed self.ObjSwitcher.DrawSwitcher(applet) /usr/lib/awn/applets/BlingSwitcher/PySwitcher.py:60: Warning: g_object_set_qdata_full: assertion `G_IS_OBJECT (object)' failed self.ObjSwitcher.DrawSwitcher(applet) /usr/lib/awn/applets/BlingSwitcher/PySwitcher.py:60: Warning: g_object_unref: assertion `G_IS_OBJECT (object)' failed self.ObjSwitcher.DrawSwitcher(applet) (awn-applet-activation:6207): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (awn-applet-activation:6207): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (nautilus:6041): Liboobs-WARNING **: There was an unknown error communicating with the backends: Did not receive a reply. Possible causes include: the remote application did not send a reply, the mess -------------------------------------------------- Traceback (most recent call last):
+ Trace 176446
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 ***