Bug 2223232

Summary:	kpat solver does not always work
Product:	[Fedora] Fedora	Reporter:	Brian Kaye <bdk>
Component:	kpat	Assignee:	Than Ngo <than>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	38	CC:	jreznik, kde-sig, rdieter, than
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-05-28 13:31:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Brian Kaye 2023-07-16 23:57:24 UTC

When running the golf game which is part of kpatience (kpat-23.04.2-1.fc38.x86_64), the solver works on the first use of the golf game but on subsequent games the solver always reports that it is unable to determine if the game can be solved. The KDE folks say the problem is fixed in 24.04.3 which fedora has not picked up. This bug is annoying because many golf games are not winnable.

Reproducible: Always

Steps to Reproduce:
1.Run golf once it works
2.run golf a second time and the solver does not work properly
3.
Actual Results:  
Golf solver fails  on second run 

Expected Results:  
Solver should say whether game is winnable or not

Comment 1 Aoife Moloney 2024-05-28 13:31:09 UTC

Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.