Bug 245738

Summary:	Undoing computer pass move removes stone
Product:	[Applications] kigo	Reporter:	Michiel Helvensteijn <mhelvens>
Component:	general	Assignee:	Sascha Peilicke <saschpe>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	kde-games-bugs
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Michiel Helvensteijn 2010-07-25 14:22:05 UTC

Version:           unspecified (using KDE 4.4.5) 
OS:                Linux

In practicing tsumego against the computer, I sometimes undo a move which the computer answered with a pass. But it seems the undo feature doesn't understand the pass move. Instead of removing the pass, it will remove the last stone played by the computer (along with my last move and the pass), giving me the next turn again.

Reproducible: Always

Steps to Reproduce:
1. Play a game against the computer, to the point that the computer will pass.
2. Make a useless move somewhere, after which the computer will pass again.
3. Undo your last move.

Actual Results:  
The useless move will be reversed, as well as the last stone played by the computer. The human player will have the next turn, likely gaining an unfair advantage. In effect, the human player will have played two consecutive moves.

Expected Results:  
The useless move and the computer pass move should be reversed, but nothing else.

Comment 1 Andrew Crouthamel 2018-11-05 03:20:55 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 2 Andrew Crouthamel 2018-11-17 04:59:27 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Justin Zobel 2022-12-15 05:49:01 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 4 Bug Janitor Service 2022-12-30 05:22:54 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bug Janitor Service 2023-01-14 05:12:00 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!