GNOME Bugzilla – Bug 429452
crash in Gimmie: apt-get in another virtu...
Last modified: 2007-04-22 22:23:23 UTC
What were you doing when the application crashed? apt-get in another virtual terminal Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy 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 (428 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80d17d0: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/chris/.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) - 0x80cf968: Received at thread b5537b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80b8590 alarm-queue.c:560 (load_alarms_for_today) - From Fri Apr 13 14:01:00 2007 to Fri Apr 13 14:01:00 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80cf968: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/chris/.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) - 0x80b7fa0:Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c00018 (tilda) 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 127530
items.append(DriveItem(drive))
icon=drive.get_icon())
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 ***