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 *** When the monitor is turned off with its power button, or the energy saver puts the screen to sleep, various KDE-based apps become unresponsive and jump to 100% CPU use (which in turn causes my CPU fan to rev up). When the monitor is turned back on and I try to focus the affected apps, it grays out and puts "(Not Responding)" in the titlebar. No amount of waiting seems to let them come back, although I can click the X on the titlebar and it'll close after a moment. Apps I know this occurs with are Konversation, KMail, Konsole, and Akregator, but I certainly haven't done extensive testing to know what other apps are or aren't affected. I do know Pale Moon and Pidgin (non-KDE apps) are not affected. STEPS TO REPRODUCE 1. Start some KDE apps. 2. Turn off the monitor, or let the power saving put the monitor to sleep. 3. Turn on the monitor. OBSERVED RESULT The aforementioned apps are unresponsive with htop showing them taking 100% CPU time. EXPECTED RESULT The apps continue to work normally. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian Linux kernel version 5.16.12, plasma-desktop package version 5.24.3-1 (available in About System) KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This only started happening when I got my new monitor, and seems to only happen under Wayland. The apps remain responsive with normal CPU use when the monitor turns off with X11. I don't know if it's related to bug #451386 at all, but both issues started for me at the same time, and both only happen with Wayland. I'm using a Radeon RX 580 and the amdgpu kernel driver, with an LG 27GP850 monitor connected via Display Port. My old monitor, which everything worked fine with, was a Samsung SyncMaster T24B350 connected via HDMI.
Please confirm if this is still an issue on 5.27, I could not immediately reproduce an issue
This doesn't seem to be happening anymore for me.
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!