After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 488189 - crash in Gimmie:
crash in Gimmie:
Status: RESOLVED DUPLICATE of bug 417988
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-19 08:48 UTC by Peng Huang
Modified: 2007-10-19 15:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Peng Huang 2007-10-19 08:48:29 UTC
What were you doing when the application crashed?



Distribution: Fedora release 7.92 (Rawhide)
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: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

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 (332 sec old) ---------------------
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
camel-Message: --
This is glChess 2.20.1
Loading AI configuration from /usr/share/glchess/ai.xml
Detected AI: GNUchess at /usr/bin/gnuchess
Loading "refresh-updatesd" plugin
(gnome-terminal:2951): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
--------------------------------------------------
Gimmie Version: 0.2.7

TypeError: <lambda>() takes exactly 1 argument (2 given)
Comment 1 H. 2007-10-19 15:38:42 UTC
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 ***