GNOME Bugzilla – Bug 491095
crash in Deskbar: login
Last modified: 2007-10-28 21:42:26 UTC
What were you doing when the application crashed? login 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: 70000000 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:393 (cal_opened_cb) exchange://ebonifazi;auth=NTLM@mail.solgenia.com/;personal/Attivit%c3%a0/Information%20System - Calendar Status 3 alarm-notify.c:393 (cal_opened_cb) exchange://ebonifazi;auth=NTLM@mail.solgenia.com/;personal/Attivit%c3%a0/My%20Credit%20Card - Calendar Status 3 alarm-notify.c:393 (cal_opened_cb) file:///home/ebonifazi/.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) - 0x80e0678: Received at thread b54fdb90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80e0200 alarm-queue.c:581 (load_alarms_for_today) - From Sun Oct 28 01:00:00 2007 to Sun Oct 28 01:00:00 2007 alarm-queue.c:518 (load_alarms) alarm-notify.c:393 (cal_opened_cb) file:///home/ebonifazi/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2052 (alarm_queue/usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format DCOPClient::attachInternal. Attach failed Could not open network socket DCOPClient::attachInternal. Attach failed Could not open network socket kbuildsycoca running... -------------------------------------------------- Traceback (most recent call last):
+ Trace 173452
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 ***