Bug 458193 - Login-Screen issue (double login of the same user possible - desktop gets useless for both logins)
Summary: Login-Screen issue (double login of the same user possible - desktop gets use...
Status: RESOLVED DUPLICATE of bug 458169
Alias: None
Product: plasmashell
Classification: Plasma
Component: Lock/logout widget (show other bugs)
Version: master
Platform: Other Linux
: NOR critical
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-23 06:42 UTC by fhgnne
Modified: 2022-08-23 13:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fhgnne 2022-08-23 06:42:03 UTC
SUMMARY
Double login is possible with the same user over the login GUI => but no double login, just two crapped logins - both unusable

STEPS TO REPRODUCE
- Start System (kubuntu 20.04 LTS - only one user available as set up during installation)
- Log in as user "user"
- Lock screen
- Choose "switch user"
- Screen switching seems to happen
- Log in now as "user" (again - no other user can be chosen here)
OBSERVED RESULT
 Log in seems to happen as for the first login, but no taskbar, autostart stuff
loads, when pressing Ctrl+Alt+F1 I get fractions of my previous login, but also
without taskbar, no real interaction with the GUI possible, etc. Pressing
Ctrl+Alt+F2 returns me to the "second" login, but this is still unusable.
- Way to get out: Either not using any gui until reboot (Ctrl+Alt+F3 => login,
sudo reboot) or sitting infinitely annoyed in front of two broken GUI logins...


EXPECTED RESULT
Either no login, because user is logged in already, return to the initial session or no second login possibility at all. At least a VERY BIG warning, that the system will become completely useless when proceeding would be helpful!

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: kubuntu 20.04 LTS (latest updates)

ADDITIONAL INFORMATION
Seems to be related to 103046 - but with the successor!
Comment 1 Nate Graham 2022-08-23 13:23:44 UTC

*** This bug has been marked as a duplicate of bug 458169 ***