GNOME Bugzilla – Bug 484331
crash in Gimmie: doing a search for restr...
Last modified: 2007-10-07 12:01:10 UTC
What were you doing when the application crashed? doing a search for restricted drivers manager Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-13-generic #1 SMP Thu Oct 4 17:18:44 GMT 2007 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 (33 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80de390: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/zach/.evolution/tasks/local/system - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80de390: Received at thread b4bfdb90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80e3260 alarm-queue.c:581 (load_alarms_for_today) - From Sun Oct 7 00:52:14 2007 to Sun Oct 7 00:52:14 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80de390: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) file:///home/zach/.evolution/memos/local/system - Calendar Status 0 alarm-queue.c:2052 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x80e5a90: ReceivedWindow manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c00062 (Buddy List) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 168482
printer.connect("attributes_changed", lambda p: self.emit("reload"))
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 475020 ***