What were you doing when the application crashed?



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 Fri Feb 1 04:59:50 UTC 2008 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 (44 sec old) ---------------------
alarm-notify.c:393 (cal_opened_cb) file:///home/jlouis/.evolution/memos/local/system - Calendar Status 0
alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:349 (alarm_msg_received) - 0x80f00c0: Received at thread b45c3b90
alarm-queue.c:2003 (alarm_queue_add_async) - 0x80f0c30
alarm-notify.c:337 (alarm_msgport_replied) - 0x80ecbd8: Replied to GUI thread
alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0
alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task
alarm-queue.c:581 (load_alarms_for_today) - From Thu Feb  7 00:00:00 2008
 to Thu Feb  7 00:00:00 2008
alarm-queue.c:518 (load_alarms) 
alarm-queue.c:547 (load_alarms) - Setting Call backs 
alarm-notify.c:349 (alarm_msg_received) - 0x80eca30: Received at thread b45c3b90
alarm-queue.c:2003 (alarm_queue_add_asyn  PID TTY          TIME CMD
--------------------------------------------------
Gimmie Version: 0.2.7

Traceback (most recent call last):

+ Trace 188453