Bug 390839

Summary:	KScreenLocker should not let you try to log in as yourself a second time
Product:	[Plasma] kscreenlocker	Reporter:	kohlhz
Component:	greeter	Assignee:	David Edmundson <kde>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	bhush94, bugseforuns, kde, mgraesslin, nate, plasma-bugs
Priority:	NOR	Keywords:	usability
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description kohlhz 2018-02-21 11:47:06 UTC

OpenSuSE Tumbleweed with all updates.
Actual state: After
  Energieverwaltung/Sitzung > Benutzer wechseln
when forgetting to change the login name.
The login seems to be successful, but then:
it's impossible to log out, change user, shut down / reboot is only possible using a command shell (if one is open!)

(At least in the last tumbleweed version it was additionally impossible to start programs beside doing that using an open window - e.g. a shell window)

Please refer to my original error message to OpenSuSE bugzilla:
https://bugzilla.opensuse.org/show_bug.cgi?id=1081469 ...

"Tumbleweed with all updates.
Situation: After
  Energieverwaltung/Sitzung > Benutzer wechseln
but the following new login is using the same login name.
The login seems to be successful, but then:
it's impossible to log out, change user, start a new program or shut down / reboot is only possible using a command shell (if one is open!)"

There you'll see, it's a very old problem, at least since the error message 2016-11-02 13:55 UTC by Ulrich Hiller 

Additional entry:
It would be very, very helpful and could be a big step forward for error correction handling to make the error message world a bit more connected.
It's really annoying to seek for the correct addressee for a bugzilla message.
The actual state is provoking the drain away of error messaging effort.

Comment 1 Nate Graham 2018-02-21 19:26:23 UTC

Sorry, it's really hard to tell what this bug is describing. Can you please write Steps To Reproduce, as outlined here? https://community.kde.org/Get_Involved/Bug_Reporting#Steps_to_Reproduce

Also see https://community.kde.org/Get_Involved/Bug_Reporting#Step_6:_File_a_high-quality_bug_report

Comment 2 kohlhz 2018-02-21 20:35:00 UTC

Reproducible: Always

Steps to Reproduce:
1. select Energieverwaltung/Sitzung > Benutzer wechseln
2. login to same user account than before
   (o.k., to open the same acoount twice is impossible in linux, the try to do that is useless - but it's only necessary to forget to select another login name)
3. use the Kontrollleiste to try to one of the following: try to logout, to reboot, to change the user correctly using the desktop

Actual Results: 
It looks like going back to the original user, but 
None of step 3 is working. To go out of this session, it's possible, to use an open shell command to reboot (but it may be even impossible, to open a new shell or to use <ctrl><alt><F5>).
Strictly reproducible.

When the login is using another user name, all is working correctly.

(I just copied that from my link to my referred message to OpenSuSE)

Expected Results, e.g.:  
one of the following:
(1) error message e.g. "you are already logged in as this user" or "you have forgotten to select a different user account"
   or 
(2) end the useless try and go back to the old job 
   or
(3) logout; login again

Comment 3 Nate Graham 2018-02-21 20:38:59 UTC

Thanks, that's very helpful.

Comment 4 Christoph Feck 2018-02-21 20:44:17 UTC

Resetting status.

Comment 5 Nate Graham 2018-02-21 20:51:25 UTC

Oops, thanks Christoph. My bad.

Comment 6 Kai Uwe Broulik 2018-02-22 07:52:13 UTC

That's SDDM, not kscreenlocker, which is a project outside of KDE. David, can you point to that upstream bug?

Comment 7 David Edmundson 2018-06-16 22:39:50 UTC

>That's SDDM, not kscreenlocker, which is a project outside of KDE. David, can you point to that upstream bug?

It's on SDDMs github, but it's now a config option to choose behaviour.


ReuseSession=true