GNOME Bugzilla – Bug 471924
crash in Deskbar: starting up
Last modified: 2007-09-03 18:09:27 UTC
What were you doing when the application crashed? starting up 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: 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-queue.c:1871 (alarm_queue_init) alarm-queue.c:200 (queue_midnight_refresh) - Refresh at Fri Aug 31 00:00:00 2007 alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/mah/.evolution/calendar/local/system alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/mah/.evolution/calendar/local/system - Calendar Open Async... 0x80b83c0 alarm-notify.c:220 (load_calendars) - Loading Calendar contacts:/// alarm-notify.c:462 (alarm_notify_add_calendar) contacts:/// - Calendar Open Async... 0x80cc330 alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/mah/.evolution/tasks/local/system alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/mah/.evolution/tasks/local/system - Calendar Open Async... 0x80d1350 alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/mah/.evolution/memos/l (evolution-alarm-notify:6307): evolution-alarm-notify-WARNING **: Could not create the alarm notify service factory, maybe it's already running... ocal/system alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/mah/.evolution/memos/local/system - Calendar Open Async... 0x80d1230 checking for valid crashreport now checking for valid crashreport now -------------------------------------------------- Traceback (most recent call last):
+ Trace 159137
self.__view.set_sensitive(True)
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find *** This bug has been marked as a duplicate of 470838 ***