On Monday 24 February 2020, Per Jessen wrote:
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.
I think I managed to reproduce the spin a couple of times by setting my Screen Locking settings for activation down to 1 minute so that it would happen more often. But I'm having trouble getting it to consistently occur. When it occurred in the same session I also saw popups concerning a kwin reset. So perhaps it is linked to compositor or window management issues. Or perhaps due to me switching to a text console to run htop. I now have a power monitor on the PC's wallplug so that when it happens I will return to see the power consumption at 125 W instead of the expected 65 W. Have you tried getting the locker to do less by setting a plain colour and or turning off the clock? When I set a plain colour I thought I'd fixed it, but it's more likely due to me logging out and logging in which would have reset kwin and the compositor. At the moment if I run the locker with no arguments its working fine with any settings I care to try: /usr/lib64/libexec/kscreenlocker_greet I wonder if there was some junk in a config file somewhere that all my playing has cleared. I noted you other message about it being a known fixed bug that may not actually be fixed. As the bug seems to be related to openGL, I might try the Display and Monitor - Compositor - Rendering backend options to see if that shakes things up a bit? That might cause more trouble I suppose. I'm totally grasping at straws here I'm afraid. I'm willing to try other experiments if it would help. Sorry to be the source of false hope. Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org