GNOME Bugzilla – Bug 494062
crash in Deskbar: i dont now ??? Distribu...
Last modified: 2007-11-08 19:05:21 UTC
What were you doing when the application crashed? i dont now ??? 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 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: Human 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 --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80eab00: Replied to GUI thread alarm-queue.c:581 (load_alarms_for_today) - From Tue Nov 6 10:28:25 2007 to Tue Nov 6 10:28:25 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80e8770: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80edb90: Received at thread b5d9fb90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80e8600 alarm-queue.c:581 (load_alarms_for_today) - From Tue Nov 6 10:28:25 2007 to Tue Nov 6 10:28:25 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80edb90: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80ef3a0: Received at threa -------------------------------------------------- Traceback (most recent call last):
+ Trace 175653
self._history.load()
saved_history = cPickle.load(file(HISTORY_FILE))
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 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: Human 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 --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80eab00: Replied to GUI thread alarm-queue.c:581 (load_alarms_for_today) - From Tue Nov 6 10:28:25 2007 to Tue Nov 6 10:28:25 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80e8770: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80edb90: Received at thread b5d9fb90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80e8600 alarm-queue.c:581 (load_alarms_for_today) - From Tue Nov 6 10:28:25 2007 to Tue Nov 6 10:28:25 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80edb90: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80ef3a0: Received at threa -------------------------------------------------- Traceback (most recent call last):
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 ***