[opensuse] Tumbleweed - kde screenlocker gobbling up a CPU ?
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). -- Per Jessen, Zürich (12.3°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
I think this is the applicable log: https://files.jessen.ch/kscreenlocker-output.txt -- Per Jessen, Zürich (13.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Sat, 22 Feb 2020, Per Jessen wrote:
On my newly installed TW system (KDE Plasma), when the screen locks, this process takes up about 100% CPU :
Nobody should use a different locker than xscreensaver anyway. See https://www.jwz.org/xscreensaver/man1.html#8 and https://www.jwz.org/blog/2015/04/i-told-you-so-again/ https://www.jwz.org/blog/2014/04/the-awful-thing-about-getting-it-right-the-... https://www.jwz.org/blog/2003/05/no-good-deed-goes-unpunished/ and especially https://www.jwz.org/xscreensaver/toolkits.html HTH, -dnh -- "Microsoft admitted its Vista operating system was a 'less good product' in what IT experts have described as the most ambitious understatement since the captain of the Titanic reported some slightly damp tablecloths." http://www.thedailymash.co.uk/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/22/2020 12:41 PM, David Haller wrote:
Hello,
On Sat, 22 Feb 2020, Per Jessen wrote:
On my newly installed TW system (KDE Plasma), when the screen locks, this process takes up about 100% CPU :
Nobody should use a different locker than xscreensaver anyway.
See https://www.jwz.org/xscreensaver/man1.html#8 and https://www.jwz.org/blog/2015/04/i-told-you-so-again/ https://www.jwz.org/blog/2014/04/the-awful-thing-about-getting-it-right-the-... https://www.jwz.org/blog/2003/05/no-good-deed-goes-unpunished/ and especially https://www.jwz.org/xscreensaver/toolkits.html
HTH, -dnh
It's things like this that really make you appreciate the fact that your kde repo has a 3 on the of it :p Still working away just fine... Just guessing here, but it looks like a fsck'ed screensaver that is threaded using mprime to compute some of the graphics and kdelocker for the display and there is a race condition (likely a screwed up mutex) that has caused the whole scheme to explode. See: 5 Big Fat Reasons Mutexes Suck Bigtime [ACCU Overload No. 149] (https://accu.org/var/uploads/journals/Overload149.pdf) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin wrote:
Just guessing here, but it looks like a fsck'ed screensaver that is threaded using mprime to compute some of the graphics and kdelocker for the display and there is a race condition (likely a screwed up mutex) that has caused the whole scheme to explode.
mprime is independent, not related to kscreenlocker. I guess I can disable the locking, although I would prefer not to. Nobody has any suggestions about what to do ? (other than using xscreensaver instead). -- Per Jessen, Zürich (12.5°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
David C. Rankin wrote:
Just guessing here, but it looks like a fsck'ed screensaver that is threaded using mprime to compute some of the graphics and kdelocker for the display and there is a race condition (likely a screwed up mutex) that has caused the whole scheme to explode.
mprime is independent, not related to kscreenlocker.
I guess I can disable the locking, although I would prefer not to. Nobody has any suggestions about what to do ? (other than using xscreensaver instead).
To disable the screenlocker, I went into System Settings->Display&Monitor->Compositor - where I see a message telling me that "openGL has crashed kwin in the past and has been disabled". I re-enabled and restarted - sure enough, kwin crashes on startup, a segfault. Any suggestions? I'm beginning to think I might go back to Leap, I just need a working system - that can be screenlocked without gobbling up a CPU :-) -- Per Jessen, Zürich (0.0°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/23/2020 03:26 AM, Per Jessen wrote:
To disable the screenlocker, I went into System Settings->Display&Monitor->Compositor - where I see a message telling me that "openGL has crashed kwin in the past and has been disabled". I re-enabled and restarted - sure enough, kwin crashes on startup, a segfault. Any suggestions? I'm beginning to think I might go back to Leap, I just need a working system - that can be screenlocked without gobbling up a CPU :-)
You know what my recommendation would be :-) I don't know of any fixes for the issue. I haven't put my hard-drive with plasma in in months (probably a good thing...) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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.) Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* 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
Michael Hamilton wrote:
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.
That's interesting - I guess the menu uses a different method. I'll have to try that.
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'll try that too although I'll need the screen to lock automatically after X minutes of inactivity.
(I've using the proprietary nvidia driver in case that's relevant.)
I have a feeling it is about video drivers, yeah. I have no fancy graphics, just built-in 82Q35 Express, driver is i915. I googled "kscreenlocker_greet" and there is a surprising number of hits about it using a lot of CPU. -- Per Jessen, Zürich (12.5°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
Michael Hamilton wrote:
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.
That's interesting - I guess the menu uses a different method. I'll have to try that.
I tried manually locking, it still invokes kscreenlocker_greet and it still loops.
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'll try that too
I tried 'loginctl lock-session' - it still invokes kscreenlocker_greet and it still loops.
(I've using the proprietary nvidia driver in case that's relevant.)
I have a feeling it is about video drivers, yeah. I have no fancy graphics, just built-in 82Q35 Express, driver is i915.
I googled "kscreenlocker_greet" and there is a surprising number of hits about it using a lot of CPU.
One of them suggested disabling 'Compositor' which I also tried - still no luck. -- Per Jessen, Zürich (13.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Per Jessen wrote:
On my newly installed TW system (KDE Plasma), when the screen locks, this process takes up about 100% CPU :
FWIW, this was/is a known bug: https://bugs.kde.org/show_bug.cgi?id=347772 kscreenlocker_greet using 100% cpu on plasma 5 https://www.phoronix.com/scan.php?page=news_item&px=Plasma-5.14-Fixes-CPU-Lock
Since May has been a bug report about the KScreenLocker greeter process going to 100% CPU usage and needing to wait 5~10 seconds after entering the user password before the screen would actually unlock.
-- Per Jessen, Zürich (13.1°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
David C. Rankin -
David Haller -
Michael Hamilton -
Patrick Shanahan -
Per Jessen