GNOME Bugzilla – Bug 485418
crash in Gimmie:
Last modified: 2007-10-11 23:11:31 UTC
What were you doing when the application crashed? 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:52:26 GMT 2007 x86_64 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 (268 sec old) --------------------- alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-queue.c:1832 (check_midnight_refresh) alarm-qchecking for valid crashreport now checking for valid crashreport now checking for valid crashreport now -------------------------------------------------- Gimmie Version: 0.3.0 Traceback (most recent call last):
+ Trace 169274
printer.connect("attributes_changed", lambda *args: 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 ***