https://bugs.kde.org/show_bug.cgi?id=468715
--- Comment #3 from Matthias Dahl <ua_bugz_...@binary-island.eu> --- My hunch was incorrect. Since I am running dbus-broker, I was expecting this to be the culprit. But after monitoring and debugging, everything is just fine and Session::activeChanged is also emitted. But nothing is wired up to actually use that signal to pause kwin. It does some udev monitoring for the drm device and for the pause and resume device from the Session but that's it. Session::activeChanged is used for the input devices, though. Could it be possible that the open source Mesa stack for example does a pause/resume device (which incidentally pauses kwin) and the proprietary nvidia driver does not thus exposing the fact that Session::activeChanged is not actually evaluated (and kwin not paused consuming high cpu)? -- You are receiving this mail because: You are watching all bug changes.
