* Michael Hamilton
On Sunday 23 February 2020, Per Jessen wrote:
On my newly installed TW system (KDE Plasma), when the screen locks, this process takes up about 100% CPU :
/usr/lib64/libexec/kscreenlocker_greet --graceTime 5000 --ksldfd 34
office25:~ # top top - 13:43:50 up 1:33, 8 users, load average: 3.00, 2.98, 2.85 Tasks: 173 total, 2 running, 171 sleeping, 0 stopped, 0 zombie %Cpu(s): 47.4 us, 0.0 sy, 52.6 ni, 0.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3633.961 total, 1308.312 free, 1117.316 used, 1208.332 buff/cache MiB Swap: 4095.996 total, 4095.996 free, 0.000 used. 2033.125 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4196 root 30 10 612232 320472 14760 S 105.0 8.612 88:47.01 mprime 10453 per 20 0 707696 126968 68092 R 94.02 3.412 17:36.51 kscreenlocker_g 1355 root 20 0 299044 78432 61900 S 0.332 2.108 0:12.58 X
(this is maybe 10minutes after it locked).
I'm not seeing that problem on my machine. I use the menu to lock the screen.
I do see the problem if if I run the command you quoted.
If I use my home brew script to lock the screen I also do not see the problem you describe:
#!/bin/bash sleep 1.5 loginctl lock-session xset dpms force suspend
(I've using the proprietary nvidia driver in case that's relevant.)
and I do very similar w/nvidia driver -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org