https://bugs.kde.org/show_bug.cgi?id=482077
--- Comment #11 from Jonathan Lopes <joniwe...@gmail.com> --- I found a way to reliably reproduce it, and a way to reliably stop it from happening (although not an ideal one). So, to make it happen, just lock the screen and move your mouse on the lock screen, then unlock. That's it. Now you have the journalctl flooded with this message. And how to reliably stop it until the next boot? > kill -9 $PID Whereas $PID is the pid of the process causing the flood in the first place, so in my case I see this in my journal: > kwin_wayland[2296]: QObject::startTimer: Timers cannot have negative intervals I run: > kill -9 2296 That's all. It'll not happen ever again until the next boot, you can lock and unlock freely. I tried to compare the processes open before and after killing kwin_wayland, but I didn't find anything relevant, other than kded5 in my case, I'll uninstall kded5 and try again, but I doubt it is the root cause. -- You are receiving this mail because: You are watching all bug changes.
