https://bugs.kde.org/show_bug.cgi?id=466178
Bug ID: 466178
Summary: kscreenlocker crash recovery advice doesn't make sense
when there are no VTs
Classification: Plasma
Product: kscreenlocker
Version: git-master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: bluescreenaven...@gmail.com
Target Milestone: ---
SUMMARY
***
The kscreenlocker recovery advice doesn't make sense when there are not VTs. to
switch back to the running session to press CTRL+ALT+F0 (since the logind VT
number is 0 when there are none). And then on the bottom, it says "you can get
back to this screen by pressing "CTRL+ALT+Fc2" where "c2" is the logind session
***
STEPS TO REPRODUCE
1. Build a kernel without VTs
2. Start KDE Plasma
3. Lock the screen
4. Kill the screen locker somehow, with an SSH session or something
OBSERVED RESULT
1. The messages are shown above, the second CTRL+ALT+Fx key that it tells the
user to press will likely vary by the logind session number
EXPECTED RESULT
Honestly I am not sure what the solution is.
CTRL+ALT+Fx bindings still work without VTs, but it's only if there is another
session to switch to
Most display manager's don't keep the greeter running, and some run the greeter
as root, so the greeter isn't a logind session for the greeter.
I almost wonder if logind would need to be amended to have a dbus command that
starts a usermode terminal on its own Wayland session on the seat, with a login
getty on i or something
This is in a similar vein as https://github.com/systemd/systemd/issues/26313
...although in this instance, kwin is usually able to respond to user key
commands, (where I opened https://github.com/systemd/systemd/issues/26313 in
the case where it's the display server that hangs solid)
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kernel 6.1
KDE Plasma Version: 5.26.80
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
--
You are receiving this mail because:
You are watching all bug changes.
