GNOME Bugzilla – Bug 442720
crash in Gimmie: Opening Open Office word...
Last modified: 2007-06-23 17:14:12 UTC
What were you doing when the application crashed? Opening Open Office word processor Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-386 #2 Wed May 23 01:42:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Outdoors Icon Theme: glass-icons 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 (3123 sec old) --------------------- alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d58d8: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80d6770: Received at thread b2d87b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d5480 alarm-queue.c:560 (load_alarms_for_today) - From Thu May 31 00:00:00 2007 to Thu May 31 00:00:00 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d6770: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/david/.evolution/calendar/local/system - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80d7248: Connecting to daemon [ ### ] Connecting to daemon [ ### ] Connecting to daemon [ ### ] Connecting to daemon [ ### ] -------------------------------------------------- Traceback (most recent call last):
+ Trace 137098
self.recent_items[recent_item.get_uri()] = recent_item
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 417988 ***