Bug 317802 - Crash on trying to open
Summary: Crash on trying to open
Status: RESOLVED WORKSFORME
Alias: None
Product: kpat
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: KDE-Windows
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-03 22:31 UTC by Doug McGarrett
Modified: 2022-02-05 04:37 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Doug McGarrett 2013-04-03 22:31:06 UTC
"We are sorry, KPatience closed unexpectedly."  Message that appears when trying to open the
program. (The graphic appears, but without the green background, so the crash must happen
sometime just before the green is loaded.) It is possible to mouse to one of the 12 game
pictures, which has its name in text, and it will turn color--green. But if you snap on that,
you get the craxh message again.  Running Classic Start Menu on Windows 8, and trying to run
the program by Start>Programs>KDE>Games>Kpatience.

Reproducible: Always

Steps to Reproduce:
Just try and open the program
2.
3.
Actual Results:  
Described above

Expected Results:  
Get a green game table-top with 12 displayed games, after which I'd pick one (Klondyke)
and it would open with the usual car layout.  This works in Windows 7, and of course, in 
PCLOS.

As mentioned, I'm running the free app, Classic Start Menu, which provides an interface that looks
just about 98% like Windows 7.
Comment 1 Andrew Crouthamel 2018-11-10 03:18:13 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-20 04:00:29 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 winblocker 2022-01-06 21:04:50 UTC
This issue still exists. My guess is this is present on large displays (i am using a 4K monitor) according to the following output when started through a terminal.

kf.coreaddons: "3840-1988-background" is too large to be cached.
kf.coreaddons: "3840-1987-background" is too large to be cached.
The Wayland connection broke. Did the Wayland compositor die?

Additional information:
kpat 21.12.1
Resolution 3840 x 2160
App launched in full screen
Comment 4 Jack 2022-01-06 21:20:23 UTC
Note the original was reported against Windows.  Also, the original report doesn't really sound like a crash, and it's not clear if this update is really a crash, or just the inability to run any of the games once the program is launched.  Also, it would be good to know if the problem really is Wayland specific, or if it also happens with xorg.  I don't have kpat installled, and it would bring in too many deps for me to bother.

I'd also be curious if those two kf.coreaddons messages are really errors or just warnings.  I suppose a backtrace might help determine that.
Comment 5 winblocker 2022-01-06 21:34:24 UTC
Oh sorry, i overlooked that this report was for windows. I retested under xorg and the game launches fine with those 2 kf.coreaddons messages. I guess my problem is wayland exclusive and should have its own report.
Comment 6 Jack 2022-01-06 21:42:39 UTC
Yes, probably best to open a new bug and let this one die of old age. 
To the OP:  does this still occur?
Comment 7 Bug Janitor Service 2022-01-21 04:37:20 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 8 Bug Janitor Service 2022-02-05 04:37:57 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!