https://bugs.kde.org/show_bug.cgi?id=512444
Bug ID: 512444
Summary: 100 % CPU used by kwin_wayland and plasmashell when
screen is locked (sometimes application are also
killed…)
Classification: Plasma
Product: kwin
Version First 6.5.3
Reported In:
Platform: Gentoo Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
Regularly, when session is locked, and screens are in powersaving mode, after a
while, kwin_wayland and plasmashell are using both 100 % CPU, until I unlock
screen.
Sometimes, also it randomly kills applications like Firefox, Thunderbird,
Signal, sometimes not, sometimes all of them, sometimes only one or two of
them.
STEPS TO REPRODUCE
1. Use a plasma session with Wayland
2. Lock Screen
3. Wait for screens to enter in powersaving mode
OBSERVED RESULT
Nearly 100 % CPU for kwin_wayland and plasmashell
EXPECTED RESULT
No 100 % CPU for kwin_wayland and plasmashell
SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux 2.18
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.17.8-gentoo-dist (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz
Memory: 32 Gio of RAM (31.3 Gio usable)
Graphics Processor: AMD Radeon RX 7800 XT
ADDITIONAL INFORMATION
I have a little alias to lock or unlock session from an ssh connection to the
corresponding computer that have this issue.
What I have observed is that only unlocking is necessary to « stop » de 100 %
CPU of kwin_wayland and plasmashell, I mean, using this alias does not wake
screens from powersaving mode, but only unlock or lock screen. So I assume the
issue is not related to screens powersaving mode, but I’m not 1000% sure.
Unfortunately it will not « definitively stop » this issue.
After a while (and sometimes it’s only 30 seconds or even less…) the issue is
back again.
And this issue happens before 6.5.3, I don’t remember when it started. I didn’t
managed to have time before, so I create this bug only now. Please, forgive me
for this.
--
You are receiving this mail because:
You are watching all bug changes.
