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 638440 - Illegal move made during game.
Illegal move made during game.
Status: RESOLVED DUPLICATE of bug 427114
Product: gnome-chess
Classification: Applications
Component: General
git master
Other Linux
: Normal major
: ---
Assigned To: JP Rosevear
JP Rosevear
Depends on:
Blocks:
 
 
Reported: 2011-01-01 06:21 UTC by avi.kurup
Modified: 2017-10-20 16:02 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
The application logs. (2.02 KB, text/plain)
2011-01-01 06:21 UTC, avi.kurup 		Details
The screenshot before the quirk. (137.02 KB, image/png)
2011-01-01 06:25 UTC, avi.kurup 		Details
Screenshot after the quirk. Captured pawn not seen. (133.96 KB, image/png)
2011-01-01 06:26 UTC, avi.kurup 		Details

Description avi.kurup 2011-01-01 06:21:55 UTC 
Created attachment 177318 [details]
The application logs.

Happy new year!!!

    I'm using glChess 2.30.0 on Ubuntu 10.04. I have been facing this quirk, where an illegal move is made by the computer
during a game. The pawn at d4 illegally captures the pawn which is moved from c2-c4. The application logs are attached. Please let me know If you need screenshots.

Any help would be great!!!
	
Thank you.
Avinash.
Comment 1 avi.kurup 2011-01-01 06:25:31 UTC 
Created attachment 177319 [details]
The screenshot before the quirk.
Comment 2 avi.kurup 2011-01-01 06:26:20 UTC 
Created attachment 177320 [details]
Screenshot after the quirk. Captured pawn not seen.
Comment 3 André Klapper 2011-01-03 22:04:20 UTC 
Closing as INVALID as per http://en.wikipedia.org/wiki/En_passant
Comment 4 Michael Catanzaro 2017-03-12 15:19:23 UTC 

*** This bug has been marked as a duplicate of bug 623648 ***
Comment 5 Michael Catanzaro 2017-10-20 16:02:05 UTC 

*** This bug has been marked as a duplicate of bug 427114 ***