GNOME Bugzilla – Bug 496422
crash in Gimmie:
Last modified: 2007-12-01 15:44:23 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-386 #1 Sun Oct 14 22:36:54 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: gnome 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 (5933 sec old) --------------------- alarm-queue.c:581 (load_alarms_for_today) - From Sat Oct 20 16:30:40 2007 to Sat Oct 20 16:30:40 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80cb970: Replied to GUI thread alarm-notify.c:349 (alarm_msg_received) - 0x80c6d78: Received at thread b3ec0b90 alarm-queue.c:2003 (alarm_queue_add_async) - 0x80c77d0 alarm-queue.c:581 (load_alarms_for_today) - From Sat Oct 20 16:30:40 2007 to Sat Oct 20 16:30:40 2007 alarm-queue.c:518 (load_alarms) alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-Window manager warning: Invalid WM_TRANSIENT_FOR window 0x280036c specified for 0x2800386 (New Docume). Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x2a00027 (Document p); these messages lack timestamps and therefore suck. -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 177401
printer.connect("attributes_changed", lambda p: self.emit("reload"))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 475020 ***