My laptop running Leap422 for testing suddenly showed me this text, white on black -
the screen locker is broken and unlocking is not possible anymore. blahblah.
I switched to a virtual console and tried running "loginctl unlock-sessions". However, this required root access ?? How does a regular office user handle this? This is a known bug. SDDM does this generally under the following premisses (reproducible for me to a 100%): a) open user A b) open user B c) try to open user A again (this will fail as it is already open). Now wait until the screensaver comes up for user A. Screen locker will now be broken and show you the message. This is an SDDM
In data venerdì 7 aprile 2017 09:52:36, Per Jessen ha scritto: problem only. If you encounter this on a regular basis use LightDM that currently does not present this issue. The reason for why a virtual console requires root to shut down is that sddm is not running afaik with the users but this suid permissions. So you need root to shut down. BTW, it is good you did remind me. I am nearly sure that this has not been fixed in 42.3 alfa but I did not try. Will give it a shot today. It may be that this is graphics dependent (I have Intel and Nvidia on another machine). Workaround: you should never open the same user session twice. Or use lightDM. I think either me or somebody else did report the but since 42.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org