https://bugs.kde.org/show_bug.cgi?id=360489
Bug ID: 360489
Summary: kscreenlocker suggests running "loginctl
unlock-sessions" even though I don't use systemd
Product: kscreenlocker
Version: unspecified
Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: aspotas...@gmail.com
CC: bhus...@gmail.com, mgraess...@kde.org
When kscreenlocker_greet is unable to start (in my case incompatible Qt
components were installed), it shows the following message:
"""
The screen locker is broken and unlocking is not possible anymore.\n
In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2),\n
log in and execute the command:\n
\n
loginctl unlock-sessions\n
\n
Afterwards switch back to the running session (Ctrl+Alt+F%1).
"""
But it is not helpful for me because I don't have systemd installed, thus I
don't have the loginctl binary. This only creates confusion.
How do I unlock session without systemd?
Reproducible: Didn't try
kscreenlocker-5.5.95
--
You are receiving this mail because:
You are watching all bug changes.
