GNOME Bugzilla – Bug 470985
crash in Deskbar: Ni idea, i strated the P...
Last modified: 2008-01-10 12:53:39 UTC
What were you doing when the application crashed? Ni idea, i strated the PC, and when i got back from the shower the PC asked me to rapport she chrash.... Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.6 2007-08-14 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Beos 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 (611 sec old) --------------------- alarm-queue.c:519 (load_alarms) alarm-queue.c:548 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80e5cc0: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80ed700: Received at thread b4d0db90 alarm-queue.c:2004 (alarm_queue_add_async) - 0x80e9cb0 alarm-queue.c:582 (load_alarms_for_today) - From Tue Aug 28 08:34:20 2007 to Tue Aug 28 08:34:20 2007 alarm-queue.c:519 (load_alarms) alarm-queue.c:548 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80ed700: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2053 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_rece PID TTY TIME CMD -------------------------------------------------- Traceback (most recent call last):
+ Trace 158408
self._history.load()
saved_history = cPickle.load(file(HISTORY_FILE)) EOFError
*** Bug 472605 has been marked as a duplicate of this bug. ***
*** Bug 473737 has been marked as a duplicate of this bug. ***
Created attachment 94997 [details] [review] Catch EOFError as well Fixes bug by catching EOFError as well as IOError.
Marking as NEW due to dupes.
*** Bug 475344 has been marked as a duplicate of this bug. ***
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
*** Bug 477717 has been marked as a duplicate of this bug. ***
*** Bug 478905 has been marked as a duplicate of this bug. ***
*** Bug 480348 has been marked as a duplicate of this bug. ***
*** Bug 480532 has been marked as a duplicate of this bug. ***
*** Bug 481382 has been marked as a duplicate of this bug. ***
*** Bug 481383 has been marked as a duplicate of this bug. ***
*** Bug 481553 has been marked as a duplicate of this bug. ***
*** Bug 481554 has been marked as a duplicate of this bug. ***
*** Bug 481879 has been marked as a duplicate of this bug. ***
*** Bug 481937 has been marked as a duplicate of this bug. ***
*** Bug 481938 has been marked as a duplicate of this bug. ***
*** Bug 482023 has been marked as a duplicate of this bug. ***
*** Bug 482024 has been marked as a duplicate of this bug. ***
*** Bug 483507 has been marked as a duplicate of this bug. ***
*** Bug 483802 has been marked as a duplicate of this bug. ***
*** Bug 483818 has been marked as a duplicate of this bug. ***
*** Bug 483825 has been marked as a duplicate of this bug. ***
*** Bug 483878 has been marked as a duplicate of this bug. ***
*** Bug 484056 has been marked as a duplicate of this bug. ***
*** Bug 484062 has been marked as a duplicate of this bug. ***
*** Bug 484063 has been marked as a duplicate of this bug. ***
*** Bug 484073 has been marked as a duplicate of this bug. ***
*** Bug 484084 has been marked as a duplicate of this bug. ***
*** Bug 484131 has been marked as a duplicate of this bug. ***
*** Bug 484195 has been marked as a duplicate of this bug. ***
*** Bug 484213 has been marked as a duplicate of this bug. ***
*** Bug 484214 has been marked as a duplicate of this bug. ***
*** Bug 484215 has been marked as a duplicate of this bug. ***
*** Bug 484216 has been marked as a duplicate of this bug. ***
*** Bug 484228 has been marked as a duplicate of this bug. ***
*** Bug 484255 has been marked as a duplicate of this bug. ***
*** Bug 484345 has been marked as a duplicate of this bug. ***
*** Bug 484354 has been marked as a duplicate of this bug. ***
*** Bug 484401 has been marked as a duplicate of this bug. ***
The proposed patch does not seem to fix the real issue here. I'm being bit by this bug about every other time I reboot my computer. I shutdown my computer using the System ... Turn off path (System->Avslutt->Slå av), so the deskbar history should be saved properly. However, this is not the case since I get the above error when I turn my computer on again. It's quite annoying to loose my deskbar history when I restart my computer, so the above solution will remove the crash but the history will still be lost. I'll attach a history file that causes the EOFError in case this will help debug the issue.
Created attachment 99643 [details] A Deskbar History Pickle that causes EOFError, resulting in crash on boot in Ubuntu Gutsy
*** Bug 499849 has been marked as a duplicate of this bug. ***
*** Bug 500019 has been marked as a duplicate of this bug. ***
*** Bug 502534 has been marked as a duplicate of this bug. ***
*** Bug 503773 has been marked as a duplicate of this bug. ***
*** Bug 507010 has been marked as a duplicate of this bug. ***
*** Bug 507638 has been marked as a duplicate of this bug. ***
*** Bug 507639 has been marked as a duplicate of this bug. ***
*** Bug 505270 has been marked as a duplicate of this bug. ***