undo move list is confused switching in and out of force

Bug #288932 reported by Jacob
6
Affects Status Importance Assigned to Milestone
gnuchess (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnuchess

gnuchess becomes confused about the move list available for "undo" when you switch it in and out of "force" to manually make moves.
Attached is a minimal typescript demonstrating this problem: A board position is set up, a move is forced, and gnuchess makes a move. At this point we should be able to undo both moves, but gnuchess only permits undoing one ply.
This disrupts playing through variations in xboard, as when you Previous Move in xboard, it sends "undo" to gnuchess, and going across a switch in "force" results in the xboard position and gnuchess position diverging.
gnuchess version is 5.07.

Revision history for this message
Jacob (jlm-ublp) wrote :
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, you can change this bug's status back to New.

Changed in gnuchess (Ubuntu):
status: New → Incomplete
Revision history for this message
Jacob Mandelson (jlm-midokura) wrote :

I tested the attached typescript from the original report with Ubuntu 10.10, and the behavior was the same, still demonstrating the bug.

Changed in gnuchess (Ubuntu):
status: Incomplete → New
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, I don't have much experience with gnuchess and your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

Thanks!

Changed in gnuchess (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Also, how are you running gnuchess and how do I use the typescript?

Revision history for this message
Jacob (jlm-ublp) wrote :

With due respect, if you can't run gnuchess, you're an inappropriate
assignee for this bug. Please reassign instead of sitting on it for
years on end.

I'm well aware of the problem of missing a crucial but unrecognized detail
when tickling software bugs. That's why I provided the *exact* input and
output, automatically captured. Your concern about it not including
"enough information" is misplaced.

I'd suggest first trying a more recent upstream version. Current is 6.0.0.

Changed in gnuchess (Ubuntu):
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.