https://bugs.kde.org/show_bug.cgi?id=347772
fle...@users.sourceforge.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Ever confirmed|0 |1
Resolution|FIXED |---
CC| |fle...@users.sourceforge.ne
| |t
--- Comment #39 from fle...@users.sourceforge.net ---
I still see this issue, completely reproducible. We are always logged in with
multiple users on the same console, switching from one account to another with
KDE's "Switch User" facility.
1) when user A locks the screen, then using the 'Switch User' button on the
locked screen, CPU is normal (~1%).
2) when user A selects the 'Switch User' from the K-menu, then I see
/usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --immediateLock
--graceTime 5000 --ksldfd 36
shooting up 100%+ on 2 cores (htop reports values from 98% to 133% sometimes).
Now if 3 users are logged in and 2 have switched accounts this way (the most
convenient actually), then 4+ cores are being maxed out, rendering the machine
unusable, and then less experienced users simply reboot it with the reset
button (sometimes by pressing it for 25 seconds, needing journal replays on
disk paritions)
My rig:
Kubuntu 18.04
libkscreenlocker5:amd64 5.12.8-0ubuntu0.1
--
You are receiving this mail because:
You are watching all bug changes.
