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 665610 - Computer says to human, "play for me!"
Computer says to human, "play for me!"
Status: RESOLVED FIXED
Product: gnome-chess
Classification: Applications
Component: General
3.7.x
Other Linux
: Normal major
: ---
Assigned To: GNOME Games maintainers
GNOME Games maintainers
Depends on:
Blocks:
 
 
Reported: 2011-12-05 16:45 UTC by rby151
Modified: 2013-05-11 19:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
This is the pgn file of the last game when this happened to me. (970 bytes, application/x-chess-pgn)
2011-12-05 16:45 UTC, rby151
Details

Description rby151 2011-12-05 16:45:14 UTC
Created attachment 202846 [details]
This is the pgn file of the last game when this happened to me.

Ok, so the computer doesn't exactly say just that. But basically, when I'm playing against the computer, sometimes the computer just doesn't move. Then, oddly, I find that I am able to choose the opposing side's move. Needless to say, it's something of a game-ruiner.
Comment 1 André Klapper 2011-12-06 13:51:50 UTC
Which version of gnome-games is this about?
Comment 2 rby151 2011-12-06 13:59:46 UTC
It's glchess 3.2.1. I'm not sure what version of gnome-games that corresponds to.
Comment 3 rby151 2011-12-06 14:02:44 UTC
But perhaps it's a problem, not with gnome-games, but with GNUChess. I downloaded PyChess and used it to play against GNUChess, and the same thing happened. Then I played a few games against PyChess and had no such problems.
Comment 4 Jeremy Bicha 2011-12-30 15:40:08 UTC
I believe this was also reported at https://bugs.launchpad.net/gnome-games/+bug/910105 . It's fairly easy to duplicate if the difficulty level is set to Hard. A human player is able to move for the computer if the computer is still thinking and hasn't made that turn's move yet. From that point on, the "computer" player is now completely computer-controlled.
Comment 5 Matthias Clasen 2012-03-20 20:13:01 UTC
Also reported at https://bugzilla.redhat.com/show_bug.cgi?id=700194
Comment 6 Thomas Andersen 2012-03-21 07:40:34 UTC
The debug output to stdout indicates that something is wrong from the very start of the game. I could sound like the computer is confused about all moves made by the human player.
Comment 7 hundfred 2012-04-11 15:48:38 UTC
after updating gnuchess on debian wheezy 

2012-04-10 10:22:03 upgrade gnuchess:i386 5.07-7 6.0.2-1

the computer (glchess,gnuchess) does not "move" any more.

here is the console output:   


** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'GNU Chess 6.0.2'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'Copyright (C) 2012 Free Software Foundation, Inc.'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'This is free software: you are free to change and redistribute it.'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'There is NO WARRANTY, to the extent permitted by law.'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'White (1) : TimeLimit[0] = 0'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[1] = 0'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[0] = 0'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[1] = 0'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[0] = 0'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[1] = 0'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'Search to a depth of 1'
** (glchess:24122): DEBUG: chess-engine.vala:146: Writing line to engine: 'force'
** (glchess:24122): DEBUG: chess-engine.vala:146: Writing line to engine: 'd2d4'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[0] = 0'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[1] = 0'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[0] = 0'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[1] = 0'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: '1. d2d4'
** (glchess:24122): DEBUG: chess-engine.vala:146: Writing line to engine: 'go'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[0] = 0'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[1] = 0'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: '1. ... b8c6'
** (glchess:24122): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'My move is : b8c6'
** (glchess:24586): DEBUG: chess-engine.vala:146: Writing line to engine: 'force'
** (glchess:24586): DEBUG: chess-engine.vala:146: Writing line to engine: 'b8c6'
** (glchess:24586): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[0] = 0'
** (glchess:24586): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[1] = 0'
** (glchess:24586): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[0] = 0'
** (glchess:24586): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'TimeLimit[1] = 0'
** (glchess:24586): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'Invalid move: b8c6'


so gnuchess seems to work correctly.
Comment 8 Dominique Leuenberger 2012-05-18 20:38:33 UTC
I just added a patch to bug 675434 which addresses that.
The issue for gnuchess is that the string:
"My move is: d2d4" changed to "My move is : d2d4"
Comment 9 Robert Ancell 2012-05-18 20:56:56 UTC
Marking as duplicate of bug 675434 based on Dominique's fix.  Please re-open if the problem still occurs after updating to the fix.

*** This bug has been marked as a duplicate of bug 675434 ***
Comment 10 Jeremy Bicha 2012-05-21 17:48:54 UTC
I can still duplicate the bug. I'm using gnome-games 3.4.2-1ubuntu3 on Ubuntu 12.10 Alpha with gnuchess 6.0.2-1.

I can still move for the computer if I move his piece before he does. Unlike before, the computer player still has control over his future turns (unless I move his piece first).
Comment 11 el 2012-09-02 13:30:51 UTC
Issue is still present with gnome-games 3.4.2/GNU Chess 5.08 on Fedora 17. In fact, GNU Chess will *NEVER MOVE*, making a game against the computer impossible.

I can move for GNU Chess as described in previous posts, but it will in fact never move on its own.
Comment 12 Dominique Leuenberger 2012-09-02 14:00:23 UTC
http://git.gnome.org/browse/gnome-games/log/?h=gnome-3-4
=> The fix was after 3.4.2;
you should be able to ask the Fedora packager to backport the fix easily
Comment 13 el 2012-09-02 16:34:49 UTC
I just fetched glchess 3.5.90 (GNU Chess version remained the same), I have the same issue with an additional oddity at startup:

- open glchess. (OTHER NEW BUG: for some weird reason, it will not only start a one minute game right away as specified in the settings, but make a white move for me although settings clearly state that human is supposed to play white. Dunno if that move is AI powered or anything, but if I move black as a response, white times out again and there is nothing like a working AI response move to my move at all. -- 100% reproducable when quitting and starting glchess again)
- click "New Game" instantly to fix the botchered game where a white move is already done
- this sets up a one minute game where human is now white as intended (at least glchess doesn't instantly do a white move now), opponent is GNU Chess
- make a move as white (which works fine)
- black clock starts running and goes down to zero without anything happening
- black loses the game

If I drag a black figure before time runs out, I can easily move for the computer as before (which I suppose I shouldn't be able to do).

Looks anything but fixed here.
Comment 14 William Makowski 2012-12-26 17:59:29 UTC
Not sure if this will solve your issue, but I had a similar problem where game would start up and make a white move.  Turned out there was an unfinished game under my history.  I exited glchess, then cleared the .local/glchess directory under my regular user and problem went away when I started a new glchess game.

I believe this unfinished game was a result of the computer not making a move because of Bug 675434.
Comment 15 Michael Catanzaro 2013-01-01 02:29:13 UTC
Funny to see that nobody has yet noted that the computer also takes over during Human vs. Human games as well.  Reproducing is trivial, just start a game against a Human and make some moves for both sides.

[michael@victory-road ~]$ export G_MESSAGES_DEBUG=all
[michael@victory-road ~]$ jhbuild run gnome-chess
Gtk-Message: Failed to load module "pk-gtk-module"
Gtk-Message: Failed to load module "canberra-gtk-module"
(gnome-chess:19957): Gtk-DEBUG: Connecting to session manager
GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings will not be saved or shared with other applications.
** (gnome-chess:19957): DEBUG: ai-profile.vala:35: Loading AI profile GNUchess
<snip>
** (gnome-chess:19957): DEBUG: ai-profile.vala:35: Loading AI profile Shredder
** Message: gnome-chess.vala:136: Detected AI profile GNUchess in /usr/bin/gnuchess
** (gnome-chess:19957): DEBUG: chess-engine.vala:153: Writing line to engine: 'xboard'
** (gnome-chess:19957): DEBUG: chess-engine.vala:153: Writing line to engine: 'easy'
** (gnome-chess:19957): DEBUG: chess-engine.vala:153: Writing line to engine: 'depth 1'
** (gnome-chess:19957): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'GNU Chess 5.08'
** (gnome-chess:19957): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'Adjusting HashSize to 1024 slots'
** (gnome-chess:19957): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'Transposition table:  Entries=1K Size=48K'
** (gnome-chess:19957): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'Pawn hash table: Entries=0K Size=32K'
** (gnome-chess:19957): DEBUG: chess-engine.vala:153: Writing line to engine: 'force'
** (gnome-chess:19957): DEBUG: chess-engine.vala:153: Writing line to engine: 'e2e4'
** (gnome-chess:19957): DEBUG: chess-engine.vala:153: Writing line to engine: 'go'
** (gnome-chess:19957): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'White (1) : move e7e5'
** (gnome-chess:19957): DEBUG: chess-engine.vala:153: Writing line to engine: 'force'
** (gnome-chess:19957): DEBUG: chess-engine.vala:153: Writing line to engine: 'c7c5'
** (gnome-chess:19957): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'Illegal move: c7c5'
** (gnome-chess:19957): DEBUG: chess-engine.vala:153: Writing line to engine: 'force'
** (gnome-chess:19957): DEBUG: chess-engine.vala:153: Writing line to engine: 'f1b5'
** (gnome-chess:19957): DEBUG: chess-engine.vala:153: Writing line to engine: 'go'
** (gnome-chess:19957): DEBUG: chess-engine-cecp.vala:41: Read from engine: 'move b8c6'
** (gnome-chess:19957): DEBUG: chess-engine-cecp.vala:49: Engine moves b8c6
Comment 16 Michael Catanzaro 2013-01-01 15:36:16 UTC
I can't reproduce it anymore and I'm not sure if I was setting my opponent to Human before each game.  So let's ignore my comment, sorry.
Comment 17 Michael Catanzaro 2013-05-11 19:54:49 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.