https://bugs.kde.org/show_bug.cgi?id=426194

Geekley <mrgeek...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INTENTIONAL                 |---
     Ever confirmed|0                           |1

--- Comment #11 from Geekley <mrgeek...@gmail.com> ---
Actually, I've done more testing and SDDM still has some of these bugs even
with ReuseSession=true. I took notes of the steps, in a "branching" form.

STEPS TO REPRODUCE AND OBSERVED RESULTS
(I merged multiple bugs I noticed when starting with the same steps, you may
need to redo a few times from start to see the other "branch")

prereq0a. ReuseSession=true in sddm conf; using always Plasma session, not
gnome
prereq0b. Have at least 2 users (in my case, they have same password, this may
be relevant!)

1. Start with a fresh (re)boot of Kubuntu (don't just logout); you're at login
screen.
2. Login User1 at SDDM
3. Winkey+L, Switch User; you're back at SDDM
3a. BUG#1! If you click Reboot, it takes a long time. It seems to be waiting at
least 1 minute or so on purpose before rebooting, but there's no visual
indication of this wait, or option to kill processes to reboot immediately
(like in Windows).

Again, from step 3:
4. Choose User2 at SDDM and login
5. Winkey+L, Switch User; User1 at tty1 is shown
6. Start New Session; you're back at SDDM
7. Login User1 again at SDDM
7a. BUG#2! You're back to lock screen of User2, not User1. At least it's asking
for the password.

8. At this lock screen, type password to go back to User2
9. CTRL+ALT+DEL, Logout
9a. BUG#3! You're now logged to User1! This time it didn't even ask for the
password (maybe having same password for both users is related to this somehow?
I didn't test with different passwords)!

10. Winkey+L, Switch User
10a. BUG#4! Now there's an Unused Session! If you use this session, you're at a
black screen with empty console prompt (tty2?). CTRL+ALT+DEL here will reboot,
again, after long wait of > 1 minute.

Again, from step 10:
11. Instead of the unused session, choose Start New Session; you're back at
SDDM
12. Try to login as User2 now (type password, enter)
12a. BUG#5! You're back to User1 again! It's asking for password. Unused is
still there!
12b. Not sure what happened here, but it seems that if you wait 1+ minute, it
goes back to SDDM on its own? Was it logging out under the hood?? I'm not 100%
sure, but I think that I just waited, because I was taking notes on a paper; I
don't think I clicked New Session.

Anyways, from step 12, quickly:
13. Login back to User1 again from that lock screen
14. CTRL+ALT+DEL, Logout
15. It does seem like you have to wait 1+ minute here... now you're back at
SDDM
16. Try to login at User2 (password, enter)
16a. BUG#6! It seems like it would have succeeded (fade out transition), but
you end up in SDDM still! If you now try User1 the same happens! You can't
login to either!

There's definitely something wrong in the way SDDM and/or Plasma is handling
these sessions. Something about tty1/tty2, I don't know. But I don't think this
happens when using GDM with Plasma.


EXPECTED BEHAVIOR

I'd expect that ReuseSession=true would make it so that those options "use this
session" or "start new session" would not even show up (it would always behave
like in step 3, even with multiple users logged in). It think this setting
should make "Switch User" in lock screen ALWAYS take you to SDDM (not stay in
lock screen to see the other sessions).

Then on SDDM (not lock screen), you'd be able to see some visual indication on
each user of whether or not they're already logged in. For example, a dot next
to the user avatar img, or some text like "(logged in)" after the user name.

And if you try to reboot or shut down from there, it should show a dialog
asking for confirmation, like: "Some users are still logged in, are you sure?";
that dialog can have the wait time of 1+ minute to kill it if you don't click
anything; or the option to cancel or shut down immediately without waiting.

And it would never use tty2 for anything GUI if I don't explicitly ask for it
(like by pressing CTRL+ALT+F2 or something). All GUI sessions are in tty1, in
fact, a novice user shouldn't even notice that this is a thing.


SOFTWARE/OS VERSIONS
OS: Kubuntu 20.04 64-bit
Linux Kernel: 5.4.0-70-generic
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to