On 09/11/2017 10:49 AM, Mick wrote:
I started a plasma session and after some period of input inactivity I noticed
the screen blanked out. Later on I moved the mouse and to my surprise I
obtained this message:
*********************
"The screen locker is broken and unlocking is not possible anymore.
In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2),
log in and execute the command:
loginctl unlock-sessions
Afterwards switch back to the running session (Ctrl+Alt+F7)."
*********************
Given this is a non-systemd Gentoo installation and I intend to keep it this
way as long as reasonably practicable, what should I instruct the user to do
to recover their current plasma session?
Are you updating KDE? I always run into this issue when updating KDE, so
I now turn off the screen lock before I commence updating.
If this is a default Gentoo installation with openrc, why does a default
plasma desktop screenlocker comes up with this nonsense?
Because KDE expects people to use systemd, a bug was raised regarding
this issue, and the developers basically said you're on your own
(RESOLVED: WONTFIX):
https://bugs.kde.org/show_bug.cgi?id=360489
According to a comment in the bug, you can try to figure out which
session it is (ck-list-sessions) and look for the X11 display property
set. This will not work (or could be difficult) if you have several
users using KDE at the same time and can't tell the sessions apart.
Once you figure that out, remember the session name and:
# su -c 'dbus-send --system --print-reply \
--dest="org.freedesktop.ConsoleKit" \
/org/freedesktop/ConsoleKit/<session name> \
org.freedesktop.ConsoleKit.Session.Unlock'
This worked on my laptop running openrc. I now just disable the locker
before doing updates.
Dan
