https://bugs.kde.org/show_bug.cgi?id=484323
--- Comment #28 from Kevin Krammer <kram...@kde.org> --- (In reply to Zamundaaa from comment #27) > KScreen being stopped preventing this isn't too surprising, as it can > trigger output changes and that seems to be what's using so much CPU, but > > or call it manually with --replace then the CPU load does no longer exceed > > normal levels > very much is. I don't really have an explanation for that one If only "kwin_x11 --replace" had worked my guess would have been a difference in environment due to being launched from an interactive shell rather than some session manager. But since killing it and having it restarted (by systemd?) also works as a "solution" that's probably not it. Could it be the order in which different components are started? Like trying to detect a D-Bus service, but failing, and falling back to some alternative code path, while succeeding when being restarted? -- You are receiving this mail because: You are watching all bug changes.
