On 7 April 2017 at 17:52, Per Jessen <per@computer.org> wrote:
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?
Probably not something a regular office user would do, but it seems the following does not require root: ``` loginctl list-sessions # Find ID that corresponds to GUI session, then run the following loginctl unlock-session <ID> ```
-- Per Jessen, Zürich (6.5°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
-- - Karl Cheng (Qantas94Heavy) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org