SUMMARY Sometimes kwin stop being responsive (clicking minimize, maximize, close, ... do nothing). The running applications are responsive, only kwin stop respond and krunner would also refuse to close/disappear when pressing escape. STEPS TO REPRODUCE It happens randomly. Sometimes often sometimes not that often but it's fairly new bug. Older versions of kde didn't have this problem. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux 2.9 (x86_64) / KDE 22.08.3 (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: Qt Version: 5.15.7 ADDITIONAL INFORMATION Systemd Journal: Jan 12 16:30:02 asus kwin_wayland[3566]: QObject::startTimer: Timers cannot have negative intervals Jan 12 16:30:04 asus kwin_wayland[3566]: QObject::startTimer: Timers cannot have negative intervals Jan 12 16:30:04 asus kwin_wayland[3566]: QObject::startTimer: Timers cannot have negative intervals Jan 12 16:30:22 asus kwin_wayland[3566]: QObject::startTimer: Timers cannot have negative intervals Jan 12 16:30:22 asus kwin_wayland[3566]: QObject::startTimer: Timers cannot have negative intervals Jan 12 16:30:23 asus kwin_wayland[3566]: QObject::startTimer: Timers cannot have negative intervals Jan 12 16:30:23 asus kwin_wayland[3566]: QObject::startTimer: Timers cannot have negative intervals Jan 12 16:30:35 asus kwin_wayland[3566]: kwin_wayland_drm: Presentation failed! Permission denied Jan 12 16:30:35 asus kwin_wayland[3566]: kwin_wayland_drm: Presentation failed! Permission denied Jan 12 16:30:37 asus kwin_wayland[3566]: QObject::startTimer: Timers cannot have negative intervals Jan 12 16:30:37 asus kwin_wayland[3566]: QObject::startTimer: Timers cannot have negative intervals Jan 12 16:32:00 asus kwin_wayland[3566]: QObject::startTimer: Timers cannot have negative intervals Jan 12 16:32:00 asus kwin_wayland[3566]: QObject::startTimer: Timers cannot have negative intervals Jan 12 16:41:41 asus kwin_wayland[3566]: kwin_libinput: Libinput: event8 - Asus Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow Jan 12 16:46:27 asus kwin_wayland[3566]: kwin_core: Could not find window with uuid "{00151e75-6cad-489d-a103-9986e2d4183d}" Jan 12 16:46:27 asus kwin_wayland[3566]: kwin_core: Could not find window with uuid "{00151e75-6cad-489d-a103-9986e2d4183d}" Jan 12 16:46:27 asus kwin_wayland[3566]: kwin_core: Could not find window with uuid "{00151e75-6cad-489d-a103-9986e2d4183d}" Jan 12 16:46:27 asus kwin_wayland[3566]: kwin_core: Could not find window with uuid "{00151e75-6cad-489d-a103-9986e2d4183d}" Jan 12 16:55:03 asus kwin_wayland[3566]: kwin_libinput: Libinput: event8 - Asus Keyboard: client bug: event processing lagging behind by 26ms, your system is too slow Jan 12 17:08:01 asus kwin_wayland[3566]: QObject::startTimer: Timers cannot have negative intervals Jan 12 17:08:01 asus kwin_wayland[3566]: QObject::startTimer: Timers cannot have negative intervals I want to note that even though the log says "system too slow", system is actually very fast and responsive with less than 10% CPU utilization.
Also worth mentioning that switching to a console (Ctrl+Alt+F<something>) then back again solve the problem but doesn't stop it from re-appearing
> kwin_wayland_drm: Presentation failed! Permission denied That message should only appear when you switch the virtual terminal. Are you sure it's happening without that as well?
I always switch to terminal when that happen in order to restore normal behavior so what you say make lot of sense. What kind of logs do I need to look for when that happen again? Assuming this message is irrelevant
You can put > QT_LOGGING_RULES="kwin_wayland_*.debug=true" into /etc/environment, that should make the logging more verbose and possibly tell us what's going on.
Created attachment 155272 [details] Systemd Journal including kwin log messages I restarted my laptop after setting the debug environment variable and when I logged in, the bug was already present. This log file should hopefully contain useful information
After repeated occurance, I noticed that this message always appears last Jan 14 08:49:53 asus kwin_wayland[3528]: This plugin does not support raise()
That warning can be safely ignored. The log unfortunately doesn't contain anything useful. I just noticed that you're using 5.25.5 though; have you tried 5.26 yet? There's a chance this is already fixed
I am using Gentoo and this is the version currently available. We can temporarily suspend this bug report if you wish and I'll get back to it once the new version is available for installation. Thanks and appreciate your help
Yeah, just reopen this if it still happens with 5.26