GNOME Bugzilla – Bug 484195
crash in Deskbar: Absturz von Evolution be...
Last modified: 2007-10-06 19:12:27 UTC
What were you doing when the application crashed? Absturz von Evolution beim Bootvorgang 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: 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 --------------------- Initializing gnome-mount extension alarm-notify.c:368 (alarm_notify_new) - Alarm Notify New alarm-notify.c:304 (alarm_channel_setup) - Channel Setup alarm-notify.c:243 (alarm_notify_init) - Initing Alarm Notify alarm-queue.c:1870 (alarm_queue_init) alarm-queue.c:200 (queue_midnight_refresh) - Refresh at Sun Oct 7 02:00:00 2007 alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/<username>/.evolution/tasks/local/system alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/<username>/.evolution/tasks/local/system - Calendar Open Async... 0x80cbf20 alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/<username>/.evolution/memos/local/system alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/<username>/.evolution/memos/local/system - Calendar Open Async... 0x80e0200 alarm-notify.c:393 (cal_opened_cb) file:///home/<username>/.evolution/tasks/local/system - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80e2e00: Rece PID TTY TIME CMD -------------------------------------------------- Traceback (most recent call last):
+ Trace 168363
self._history.load()
saved_history = cPickle.load(file(HISTORY_FILE)) EOFError
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 470985 ***