SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Start a game. 2. Make it full screen. 3. OBSERVED RESULT Hangs for a while small on the top left and after 4 seconds exits. EXPECTED RESULT Play the game. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
How do you even get ksudoku running on windows?
(In reply to Albert Astals Cid from comment #1) > How do you even get ksudoku running on windows? By running Ksudoku on Kubuntu as a guest machine in VMware.
Ok, what about reading the text that you should have read, i will post it again. NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports We need a backtrace
(In reply to Albert Astals Cid from comment #3) > Ok, what about reading the text that you should have read, i will post it > again. > > NOTE: If you are reporting a crash, please try to attach a backtrace with > debug symbols. > See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > > We need a backtrace In: https://wiki.kubuntu.org/DebuggingProgramCrash I get: (404) Not Found The requested URL was not found on this server. Apache/2.4.41 (Ubuntu) Server at wiki.kubuntu.org Port 443 And when I run in terminal: ~$ sudo apt install ksudoku-dbg Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package ksudoku-dbg
(In reply to Albert Astals Cid from comment #3) > Ok, what about reading the text that you should have read, i will post it > again. > > NOTE: If you are reporting a crash, please try to attach a backtrace with > debug symbols. > See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > > We need a backtrace By the way: I installed Kubuntu 22.04.1 on hardware and not VMware and still the same bug when making Ksudoku full screen in 4K resolution, but now with 2K resolution in another screen to the left, still with the taskbar on the right as panel.
(In reply to Albert Astals Cid from comment #3) > Ok, what about reading the text that you should have read, i will post it > again. > > NOTE: If you are reporting a crash, please try to attach a backtrace with > debug symbols. > See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > > We need a backtrace How do I edit a comment in here please?
As far as I understand you can't edit comments. I'll ask the Kubuntu people to update the instructions.
The crash doesn't happen for me anymore on a 4K display with a 2K display on the left with the taskbar on the right after a Kubuntu system update. Cheers!