https://bugs.kde.org/show_bug.cgi?id=484323
Zamundaaa <xaver.h...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |CONFIRMED
--- Comment #27 from Zamundaaa <xaver.h...@gmail.com> ---
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
--
You are receiving this mail because:
You are watching all bug changes.
