GNOME Bugzilla – Bug 447704
crash in Gimmie: Opening a .zip file
Last modified: 2007-06-23 17:21:31 UTC
What were you doing when the application crashed? Opening a .zip file 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 (1691 sec old) --------------------- alarm-notify.c:349 (alarm_msg_received) - 0x80dacd8: Received at thread b3561b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80d5380 alarm-queue.c:560 (load_alarms_for_today) - From Thu Jun 14 00:00:00 2007 to Thu Jun 14 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) - 0x80dacd8: Replied to GUI thread 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-notify.c:349 (alarm_msg_received) - 0x80ddbe0: Connecting to daemon [ ### ] Connecting to daemon [ ### ] Connecting to daemon [ ### ] Connecting to daemon [ ### ] Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c0006c (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c0006c (OpenOffice) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. -------------------------------------------------- Traceback (most recent call last):
+ Trace 141069
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 ***