GNOME Bugzilla – Bug 494578
crash in Gimmie: trying to start gimmie
Last modified: 2007-11-07 23:01:58 UTC
What were you doing when the application crashed? trying to start gimmie 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-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: Murrina-IndustrialSM Icon Theme: Cassandra 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 (5321 sec old) --------------------- GTK Accessibility Module initialized DOUBLE-CLICK: 400 --> -1 THRESHOLD: 8 --> -1 (Gecko:13001): GLib-GObject-WARNING **: gsignal.c:1019: unable to lookup signal "activate" of unloaded type `MaiAtkObject' (Gecko:13001): GLib-GObject-CRITICAL **: g_signal_emit_valist: assertion `signal_id > 0' failed GTK Accessibility Module initialized ** Message: ATK_ROLE_TOOLTIP object found, but doesn't look like a tooltip. ** Message: ATK_ROLE_TOOLTIP object found, but doesn't look like a tooltip. ** Message: ATK_ROLE_TOOLTIP object found, but doesn't look like a tooltip. GTK Accessibility Module initialized Bonobo accessibility support initialized Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5e00003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. GTK Accessibility Module initialized Bonobo accessibility support initialized -------------------------------------------------- Gimmie Version: 0.2.7 TypeError: <lambda>() takes exactly 2 arguments (1 given)
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 ***