https://bugs.kde.org/show_bug.cgi?id=496777
--- Comment #1 from Rocnir <odd...@gmail.com> ---
It just happened again, after the very first suspend and a wakeup only a couple
of minutes later. But I tried something new.
Instead of entering my password I went to tty1 (Ctrl+Alt+F1), and my session
was still there. Loginctl showed:
```SESSION UID USER SEAT TTY STATE IDLE SINCE
1 1000 rocnir seat0 tty1 active no
c1 983 sddm seat0 tty3 online no```
Note that my session state says 'active'.
Before I could kill the sddm session with `loginctl terminate-session c1` the
lock screen appeared again, about 30 seconds after switching to tt1. I returned
to tty1 again without logging in, and immediately did `loginctl` again and got:
```SESSION UID USER SEAT TTY STATE IDLE SINCE
1 1000 rocnir seat0 tty1 closing no
c1 983 sddm seat0 tty3 online no
c2 983 sddm seat0 tty2 online no```
So the second lock screen appears to have been shown on tty2, and my session
state changed to 'closing'.
--
You are receiving this mail because:
You are watching all bug changes.
