Bug 420547

Summary: Klondike Solver reports "No Longer Winnable" due to autoplay
Product: [Applications] kpat Reporter: Clifford K <clkeele>
Component: solverAssignee: Stephan Kulow <coolo>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kde-games-bugs-null
Priority: NOR    
Version First Reported In: 3.6   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: See Game Above, Klondike 195197386

Description Clifford K 2020-04-25 09:00:51 UTC
Created attachment 127848 [details]
See Game Above, Klondike 195197386

SUMMARY
Autoplay kicks in and starts playing cards off of the deck forcing the game into "No Longer Winnable".  In this case, top card on deck is an Ace.  Solution requires playing the two cards on top of the ace, and leaving the ace.  The game autoplays the ace, reporting "No Longer Winnable".  Even when one reverses, it still says "No Longer Winnable" until one hits the next deal when it turns back to "Winnable".

STEPS TO REPRODUCE
1. See attached game.  First (bottom) card triggers autoplay, but is incorrect, and should not be played, creating "unwinnable".
2.  Undo, and ace is brought back to the top, and it still reports "This game no longer winnable",
3.  Deal next 3 cards off of the deck, and it correctly reports "winnable" (move after unwinnable).  In this case, a second time through the deck and one can play the queen followed by the jack.

OBSERVED RESULT
System reports "This Game is Unwinnable followed by "This game is Winnable" with next move.

EXPECTED RESULT
No Autoplay.  Game reports only "Winnable" as long as Ace isn't played until the end.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 31
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.13.2
KPatience 3.6

ADDITIONAL INFORMATION
Comment 1 Stephan Kulow 2023-03-09 05:05:03 UTC
The saved game is in a broken state due to undo/redo. This needs fixing and is not about klondike or the solver.

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