https://bugs.kde.org/show_bug.cgi?id=496777
--- Comment #2 from Rocnir ---
Happened another two times since my last comment yesterday.
Today was so bad I couldn't login at all, I just got a black screen after
entering my password on the lock screen, on all ttys that i tried. On one
https://bugs.kde.org/show_bug.cgi?id=496777
--- Comment #1 from Rocnir ---
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
AT TTY STATE IDLE SINCE
1 1000 rocnir seat0 tty1 closing no
3 983 sddmseat0 tty2 online no```
Compare that with the normal state, prior to the suspend and before the bug
happens:
```SESSION UID USER SEAT TTY STATE IDLE SINCE
https://bugs.kde.org/show_bug.cgi?id=496793
Bug ID: 496793
Summary: Lock screen is presented despite it being disabled
Classification: Plasma
Product: kscreenlocker
Version: 6.2.3
Platform: Solus
OS: Linux
Statu
https://bugs.kde.org/show_bug.cgi?id=496793
--- Comment #1 from Rocnir ---
Created attachment 176192
--> https://bugs.kde.org/attachment.cgi?id=176192&action=edit
Settings for automatic login
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=496777
Rocnir changed:
What|Removed |Added
Summary|Lock screen after wake up |Lock screen after wake up
|causes
https://bugs.kde.org/show_bug.cgi?id=496777
--- Comment #3 from Rocnir ---
I have discovered two more details.
1. As the 'loginctl' output shows, the lockscreen is always presented on tty2.
HOWEVER, by going to tty1 (Ctrl+Alt+F1) I am back in my session and can bypass
the lockscre
https://bugs.kde.org/show_bug.cgi?id=496777
--- Comment #9 from Rocnir ---
The same bug occurred in the test account as well just a short while ago: got a
lock screen despite having disabled it.
Entered the password and switched user (to my regular account), which led to a
bunch of issues
https://bugs.kde.org/show_bug.cgi?id=496777
--- Comment #7 from Rocnir ---
So I rebooted with my regular user and suspended and woke up the PC after about
15 seconds. I did this several times, with no problem.
I then suspended and waited about 5 min before waking up, and got the reported
bug
https://bugs.kde.org/show_bug.cgi?id=496777
--- Comment #5 from Rocnir ---
So it just happened again as I woke up the computer to reply (it was the first
suspend + wake up today after a fresh boot this morning).
But instead of going straight to tty1 I entered the password (on tty2 I
presume
https://bugs.kde.org/show_bug.cgi?id=496777
--- Comment #6 from Rocnir ---
Created attachment 176564
--> https://bugs.kde.org/attachment.cgi?id=176564&action=edit
Dialog after wakeup
The dialog presented after bypassing the lockscreen by going to tty1.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=496777
--- Comment #8 from Rocnir ---
Preliminary result is that a new user account does not have this issue, I have
not been encountered the bug so far after multiple suspend + wake ups.
The only thing I can think of is that I installed 'dotool'
12 matches
Mail list logo
