Bug 357349 - In Spider Solitaire an extra card gets sent to completed piles
Summary: In Spider Solitaire an extra card gets sent to completed piles
Status: RESOLVED WORKSFORME
Alias: None
Product: kpat
Classification: Applications
Component: general (show other bugs)
Version: 3.6
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-30 19:43 UTC by Tim Middleton
Modified: 2022-11-18 05:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
screen shot of 2 of clubs in wrong place (322.05 KB, image/png)
2015-12-30 19:44 UTC, Tim Middleton
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Middleton 2015-12-30 19:43:35 UTC
In spider solitaire when you complete a full sequence of the same suite the cards get moved from the playing area to the "completed pile". In one instance, I got to the end of the game I was about to win and found there was a card missing in the play area. Looking down on the completed pile, which normally will show the ace at the top of each pile, one pile shows a 2 of clubs, which is the missing card from the play area. 

It actually seems like the pile where the 2 of clubs is showing thinks it is the completed clubs set, because there are two of each suits represented in the complete piles (I play with "4 suits (hard)" option), despite there being all the other clubs except the 2 still in the play area. 

I have taken a screen shot to show how the game looks in the current error state which I will attach to a comment.

Since the completed piles exist in order that they were completed and the 2 of clubs appears in the 4th pile, it seems the bug happened some turns ago and I didn't notice.

Thinking back, I did notice one strange behaviour, however. At one point I completed a suit and it failed to auto-move to the completed piles. I then moved that completed card sequence to an empty spot and that triggered it to move itself to the completed piles. Perhaps that is when the weird state appeared.

I see the game number is 1123469748, but I haven't yet tried to replay this game and see if I can trigger the problem again. 

Reproducible: Didn't try
Comment 1 Tim Middleton 2015-12-30 19:44:56 UTC
Created attachment 96369 [details]
screen shot of 2 of clubs in wrong place
Comment 2 Tim Middleton 2015-12-30 23:15:32 UTC
I hit undo until I reached the place where the 2 of clubs was put down. I can confirm it was at the same time as the completed sequence which did not auto-move to the completed piles happened. Hitting redo at that point would repeat the same error. However, if I completed the sequence again from a save game I made at that point then it moved to the completed pile properly and the 2 of clubs remained in play....

So, I can not repeat the bug.
Comment 3 Justin Zobel 2022-10-19 02:59:53 UTC
Thank you for reporting this bug 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 "CONFIRMED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-11-03 05:07:05 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 2022-11-18 05:17:19 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!