Created attachment 519396 [details] consolekit unlocker script During large updates to KDE and/or QT the screen locker in KDE can malfunction and have it reset. More specifically, the message is: "The screen lock is broken and unlocking is not possible any more. 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). " If you are using openrc loginctl does not work as it is part of systemd. There are a few reports of this problem on the forums and on gentoo-user. I forgot to disable the screenlocker while doing a major update and hit this again. KDE has bug: https://bugs.kde.org/show_bug.cgi?id=360489 but will not fix the problem, citing a corner case. There is a solution in there to use dbus to send a message to unlock the session, and I've taken that and put it into an initial bash script. The script will allow you to attempt to unlock all sessions or list and specify a specific session to unlock. As my screen locker was currently broken I've been able to test it various ways to make sure it works. I've attached the bash script in case others looking for a solution to this problem. It's simply called ck-unlock-session. I also looked for the "Annoying" option under Severity but it wasn't there! ;)
It is not a matter of openrc, but consolekit vs. elogind. Before stabilising KDE Plasma 5.12.x we are going to make the transition to elogind, this will solve several problems, this being among them.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/kde.git/commit/?id=50141c4028e664727b1006319ddd44b3cc50eb31 commit 50141c4028e664727b1006319ddd44b3cc50eb31 Author: Michael Palimaka <kensington@gentoo.org> AuthorDate: 2018-02-17 01:13:31 +0000 Commit: Michael Palimaka <kensington@gentoo.org> CommitDate: 2018-02-17 01:15:48 +0000 kde-plasma/kscreenlocker: add support for killing the screenlocker on consolekit Original script by Daniel Frey <djqfrey@gmail.com>. Modifications by Lars Wendler <polynomial-c@gentoo.org>. Bug: https://bugs.gentoo.org/647576 Package-Manager: Portage-2.3.19, Repoman-2.3.6 kde-plasma/kscreenlocker/files/ck-unlock-session | 220 +++++++++++++++++++++ .../files/kscreenlocker-consolekit-unlock.patch | 13 ++ .../kscreenlocker-5.12.49.9999.ebuild | 6 +- kde-plasma/kscreenlocker/kscreenlocker-9999.ebuild | 6 +- kde-plasma/kscreenlocker/metadata.xml | 3 + 5 files changed, 246 insertions(+), 2 deletions(-)}
Upstream fix: https://cgit.kde.org/kscreenlocker.git/commit/?id=68fb0b7d3e1c9358c84aa9ab095a4a3bfb75540a
(In reply to Arfrever Frehtes Taifersar Arahesis from comment #3) > Upstream fix: > https://cgit.kde.org/kscreenlocker.git/commit/ > ?id=68fb0b7d3e1c9358c84aa9ab095a4a3bfb75540a The patch needs to be removed from kscreenlocker-9999.ebuild.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/kde.git/commit/?id=830efe98263d5e761b7da9d6cdb45104f52b68cd commit 830efe98263d5e761b7da9d6cdb45104f52b68cd Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2018-03-19 17:14:20 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2018-03-19 17:14:20 +0000 kde-plasma/kscreenlocker: Drop custom ck-unlock-session for >=5.13 Upstream commit 68fb0b7d3e1c9358c84aa9ab095a4a3bfb75540a Bug: https://bugs.gentoo.org/647576 Package-Manager: Portage-2.3.24, Repoman-2.3.6 kde-plasma/kscreenlocker/kscreenlocker-9999.ebuild | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-)}
KDE Plasma 5.12.5 is stable.
