GNOME Bugzilla – Bug 485056
crash in Deskbar: Crash always happens dua...
Last modified: 2007-10-09 19:29:27 UTC
What were you doing when the application crashed? Crash always happens duaring booting. It happens right after I upgraded to Gutsy from Feisty Fawn Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: tango-noir0-8.0 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 --------------------- alarm-queue.c:2003 (alarm_queue_add_async) - 0x80d9860 alarm-queue.c:581 (load_alarms_for_today) - From Tue Oct 9 17:10:19 2007 to Tue Oct 9 17:10:19 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80dd270: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80daec0: Received at threa/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format (awn-applet-activation:5897): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed (awn-applet-activation:5897): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed PID TTY TIME CMD -------------------------------------------------- Traceback (most recent call last):
+ Trace 169020
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 ***