https://bugs.kde.org/show_bug.cgi?id=498941
Bug ID: 498941
Summary: High iGPU utilisation of plasmashell/kwin_wayland
while panel hidden
Classification: Plasma
Product: plasmashell
Version: 6.2.5
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Panel
Assignee: plasma-b...@kde.org
Reporter: deinor...@gmail.com
CC: niccolo.venera...@gmail.com
Target Milestone: 1.0
SUMMARY
I have a ThinkPad T490 with a Core i5 8365U, which is important, as I guess, a
way more powerful Desktop system won't see any substantial utilisation over the
usual with a performant graphics card, as the 2018/2019 Intel iGPU is weak.
I have been getting this symptom for months irregularly (probably since Plasma
6?), but right now it's especially annoying, and I found out, how I could
reproduce it better.
STEPS TO REPRODUCE
Caution: This doesn't happen all the time, only at specific times I can't be
sure of.
1. System panel is set to hidden, where you can get it up with the mouse.
Floating panel or not doesn't seem to matter, as this bug isn't there, when the
panel is generally shown.
2. Switch between apps with Alt-Tab or to yakuake with F12 without the panel
popping up.
OBSERVED RESULT
High iGPU utilisation (60-80 %) while doing nothing and opened programs. When I
move the mouse to the system panel to bring it up, utilisation goes down to
normal level.
If I'm correct, I could recognise this more often after a system update and
cold restart (no soft reboot). After another reboot it went away, and I didn't
think about it any longer, until it came back and because I'm on a laptop I can
hear this.
EXPECTED RESULT
No high utilisation out of the blue.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch linux-zen 6.12.10
KDE Plasma Version: 6.2.5 @ wayland
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1
ADDITIONAL INFORMATION
Right now I couldn't reproduce this with another user account on the same
laptop and OS, but I accidentally rebooted the system, so I can't say, if the
reboot did help or the new user. Back to my normal account, it went away as
usual.
Is there a way to check, what calls contribute to this? Is dmesg an option, of
which I didn't think earlier ...
--
You are receiving this mail because:
You are watching all bug changes.
