GNOME Bugzilla – Bug 448055
crash in Gimmie: opening a .jpg file with...
Last modified: 2007-06-23 17:14:00 UTC
What were you doing when the application crashed? opening a .jpg file with the gthumb image viewer 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 Thu Jun 7 20:16:13 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 (5237 sec old) --------------------- 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:393 (cal_opened_cb) file:///home/david/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80d83c0: Received at thread b35d1b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d5380 alarm-notify.c:337 (alarm_msgport_replied) - 0x80d9098: Replied to GUI thread alarm-queue.c:560 (load_alarms_for_today) - From Fri Jun 15 00:00:00 2007 to Fri Jun 15 00:00:00 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80e13b8: Received at thread b35d1b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80 Connecting to daemon [ ### ] Connecting to daemon [ ### ] Connecting to daemon [ ### ] Connecting to daemon [ ### ] Co -------------------------------------------------- Traceback (most recent call last):
+ Trace 141331
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 ***