SUMMARY When I use KDE neon the desktop seems to sometimes randomly freeze. STEPS TO REPRODUCE I have no idea how to reproduce this bug. First it seemed to be related to Opera, because it would often freeze when I opened a new window, but recently I got the same freeze when I opened JOSM. The only thing I did was to open a Windows: So for Opera: Right Click + New (private) Window. When I got the freeze with JOSM I opened it through the start menu OBSERVED RESULT The desktop freezes entirely. If music or a video is playing, the audio enters a loop of about 2 seconds. The desktop does not react to anything anymore. No clicks, no mouse, no keypresses, no Ctrl + Alt + F6 - nothing. When I had some time I let the PC sit and see if it does somehow get back on it's feet. Since it did not change after 20 minutes I gave up. The only 'fix' I could work out is to hard reset the PC. EXPECTED RESULT A nice BSOD crash would help since it would save me the work or pressing the restart button. Optionally I would of course prefer the system to not-crash and not-freeze since it's usually bad for the workflow :-) SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.13.0-44-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 30.8 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION I have no idea if this is the right component since I have no idea what even causes the crash. I read about random freezes online with other distros as well which describe a similar pattern on Debian (Including Ubuntu) and Arch (including Manjaro) based systems. Though I have no idea if they are related or not.
Random freezes can be due to other reasons than plasma. I used to get random freezes due to resetting of my GPU driver on launching chromium/electron and had to add a kernel parameter to fix it. Nevertheless, this can be a plasma bug and for crashes we need a crash report to proceed. You can refer the guide here: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
(In reply to Bacteria from comment #1) > Nevertheless, this can be a plasma bug and for crashes we need a crash > report to proceed. You can refer the guide here: > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports I will take a look into this. Since the bug seems to randomly occur it will take some time though.
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!
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!