GNOME Bugzilla – Bug 490975
crash in Gimmie: Starting Gimmie from gno...
Last modified: 2007-10-28 12:33:29 UTC
What were you doing when the application crashed? Starting Gimmie from gnome-terminal Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.20.1 2007-10-15 (Red Hat, Inc) BugBuddy Version: 2.20.0 System: Linux 2.6.23.1-23.fc8 #1 SMP Wed Oct 17 18:12:05 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks-Pastel Icon Theme: OSX 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 (105212 sec old) --------------------- Checking for GLX_SGIX_fbconfig : passed Checking for GLX_EXT_texture_from_pixmap : passed Checking for non power of two texture support : passed Checking maximum texture size : passed (4096x4096) Reloading options Window manager warning: Workarounds for broken applications disabled. Some applications may not behave properly. ** Message: Could not connect to power manager: Could not get owner of name 'org.freedesktop.PowerManagement': no such name ** Message: Could not connect to power manager: Could not get owner of name 'org.freedesktop.PowerManagement': no such name ** Message: Could not connect to power manager: Could not get owner of name 'org.freedesktop.PowerManagement': no such name Window manager warning: CurrentTime used to choose focus window; focus window may not be correct. Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen! Failed to kill esd (pid 30535) Data updated for username helen_ken. Data updated for username helen_ken. -------------------------------------------------- Gimmie Version: 0.2.7 TypeError: <lambda>() takes exactly 1 argument (2 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 ***