What were you doing when the application crashed?



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 (7 sec old) ---------------------
 alarm-notify.c:304 (alarm_channel_setup) - Channel Setup
 alarm-notify.c:243 (alarm_notify_init) - Initing Alarm Notify
alarm-queue.c:1871 (alarm_queue_init)
alarm-queue.c:200 (queue_midnight_refresh) - Refresh at Wed Aug 29 03:00:00 2007
 
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/furyy/.evolution/calendar/local/system 
alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/furyy/.evolution/calendar/local/system - Calendar Open Async... 0x80b8540
alarm-notify.c:220 (load_calendars) - Loading Calendar contacts:/// 
alarm-notify.c:462 (alarm_notify_add_calendar) contacts:/// - Calendar Open Async... 0x80d95d0
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/furyy/.evolution/tasks/local/system 
alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/furyy/.evolution/tasks/local/system - Calendar Open Async... 0x80dda30
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/furyy/.evoluti
(evolution-alarm-notify:15296): evolution-alarm-notify-WARNING **: Could not create the alarm notify service factory, maybe it's already running...
on/memos/local/system 
alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/furyy/.evolution/memos/local/system - Calendar Open Async... 0x80e2a00
--------------------------------------------------
Traceback (most recent call last):

+ Trace 158598