https://bugs.kde.org/show_bug.cgi?id=373368
Edward Kigwana <edwardw...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |edwardw...@gmail.com
--- Comment #16 from Edward Kigwana <edwardw...@gmail.com> ---
On my workstation with opengl I do not have this issue. In my VMs and on a
target system without opengl (modesetting) atom bay trail cpu usage is so
excessive that the interface starts glitching almost as though I was trying to
run plasma on an i386@25 MHz. I can see the drawing sequences.
Editing
/usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationIcon.qml
and setting PlasmaComponents.BusyIndicator { running: active } to
PlasmaComponents.BusyIndicator { running: false } and everything goes back to
what I'd expect. On a side note sddm also has high CPU usage on the VM and the
the Intel atom system. This issue appears for me on systems using the xrender
code paths and when QML is involved it seems.
--
You are receiving this mail because:
You are watching all bug changes.
