Bug 465032 - Golf crashes in winnable game when talon is empty
Summary: Golf crashes in winnable game when talon is empty
Status: RESOLVED DUPLICATE of bug 424263
Alias: None
Product: kpat
Classification: Applications
Component: general (other bugs)
Version First Reported In: 22.12.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-30 10:00 UTC by Alex Dubov
Modified: 2023-01-30 11:52 UTC (History)
1 user (show)

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


Attachments
Golf save game (9.63 KB, application/xml)
2023-01-30 10:11 UTC, Stephan Kulow
Details
Save game for game 671362933 (9.65 KB, application/vnd.kde.kpatience.savedgame)
2023-01-30 10:26 UTC, Alex Dubov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Dubov 2023-01-30 10:00:20 UTC
Upon playing a winnable game of golf, kpat crashes when talon becomes empty. There may still be multiple playable cards on the tableau.

If talon is not empty, the game completes as expected with some card animation.

Most other games work fine.

STEPS TO REPRODUCE
1.  Play the game to win in such a way, as to have an empty talon at victory.
2.  Observe the crash.

SOFTWARE/OS VERSIONS
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Comment 1 Stephan Kulow 2023-01-30 10:06:01 UTC
Do you have a same game short before the event by chance?
Comment 2 Stephan Kulow 2023-01-30 10:11:14 UTC
Created attachment 155781 [details]
Golf save game

Does not crash to me
Comment 3 Alex Dubov 2023-01-30 10:26:50 UTC
Created attachment 155782 [details]
Save game for game 671362933

Attached a save for game which crashed for me.
At the save point: clicking 10 - 9 - 10 - talon causes am immediate termination of kpat.
Comment 4 Stephan Kulow 2023-01-30 11:51:17 UTC
Nope - works fine, but I have 23.03.70 here.
Comment 5 Stephan Kulow 2023-01-30 11:52:35 UTC
It looks fixed in december

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