Bug 435496

Summary:	No way for switch back to unlock screen after click on "Switch user" button
Product:	[Unmaintained] kscreenlocker	Reporter:	Murz <MurzNN>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	bshah, nate
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
URL:	https://github.com/sddm/sddm/issues/579
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Murz 2021-04-08 06:49:20 UTC

The kscreenlocker screen have the "Switch user" button, but when user click on it - there is no way to go back to unlock screen for current user, so this button makes gives one-way way :)

The hacky workaround is to use hotkeys Ctrl-Alt-# to switch between sessions, but not all knows about this.

Seems proper fix must be done in SDDM side (using some integration with kscreenlocker maybe?), but maybe possible to implement something from KDE side? At least warning or message how to switch back, on this key press event?

Comment 1 Nate Graham 2021-04-09 02:27:40 UTC

Just log back into your own user account. Is that not working for you?

Comment 2 Murz 2021-04-09 07:07:02 UTC

If I enter my credentials in "Switch user" screen (SDDM), it creates the new (second) separate session for my user, instead of switching back to already active session.

Maybe this is missing feature in SDDM to show also list of all active sessions to switch?

Comment 3 Murz 2021-04-09 07:11:37 UTC

I have found the related SDDM issue https://github.com/sddm/sddm/issues/579 about this problem.

Comment 4 Nate Graham 2021-04-09 20:02:18 UTC

Yeah, having https://github.com/sddm/sddm/issues/579 implemented would fix it. Also, you can fix it for yourself by setting ReuseSession=true to your SDDM config file. This is supposedly the new default setting in SDDM, so one of the following is happening:

1. It's broken in SDDM and is not actually the new default setting (boo)
2. Arch is overriding it by shipping a config file that sets it to false
3. You or something else manually set it to false in your locla config file.

Either way, not a KDE issue. :)