SUMMARY Logging in and out of a session while leaving a second one "locked" creates a bunch of "unused" sessions. STEPS TO REPRODUCE 1. Login to account A and switch users (should stay in background 2. Log in to account B and then log out 3. Open account A once again and switch users, you will see an "unused" session in the menu. 4. Repeat the same process N times and you will get N "unused" sessions. OBSERVED RESULT https://i.imgur.com/vS4MOWD.jpg EXPECTED RESULT Just switching users with no "unused" sessions. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.55.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION I'm Fedora 29 KDE spin
This was fixed in Plasma 5.15.
Created attachment 121486 [details] Unused sessions It's not resolved yet. This screenshot is from today on Plasma 5.15.5. I've also had it happen several times before. It eventually cleans up but it's not predictable.. and if I select one of the "unused" sessions the session might never log the second user in (remains loading the desktop, blank screen) and I have to use the hotkey to get back to the first user and kill the other users processes.
Sometimes when I try to go back to the previous user the screen just stays blank, no login occurs and it just hangs there and I have to force-restart my machine. Changing user sessions is basic guys and it has always been very unreliable in Plasma, you need to figure this out.
FWIW, I see a geoclue agent process running even after I called `loginctl terminate-user`. The unused session goes away when I kill that process.
I can confirm now.
*** Bug 416557 has been marked as a duplicate of this bug. ***
bug 401928 seems related
*** Bug 426980 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 422322 ***
This is actually a duplicate of Bug 355920 instead, which turned out to be an SDDM issue which was fixed in version 0.19. *** This bug has been marked as a duplicate of bug 355920 ***
*** Bug 372275 has been marked as a duplicate of this bug. ***