https://bugs.kde.org/show_bug.cgi?id=470432
silentdoer <1010993...@qq.com> changed:
What|Removed |Added
CC||1010993...@qq.com
--- Comment #
https://bugs.kde.org/show_bug.cgi?id=470432
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINF
https://bugs.kde.org/show_bug.cgi?id=470432
--- Comment #6 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular b
https://bugs.kde.org/show_bug.cgi?id=470432
--- Comment #5 from Nate Graham ---
Thanks. In step 4, if you wake the monitor by clicking the mouse or pressing a
modifier key like Ctrl, does the problem still happen in step 5?
--
You are receiving this mail because:
You are watching all bug change
https://bugs.kde.org/show_bug.cgi?id=470432
--- Comment #4 from Matt Keith ---
(In reply to Nate Graham from comment #3)
> So the first time you try to enter your password, it's rejected, and the
> second time, it works?
Correct
>
> Can you elaborate on why you think the enter key is involved he
https://bugs.kde.org/show_bug.cgi?id=470432
--- Comment #3 from Nate Graham ---
So the first time you try to enter your password, it's rejected, and the second
time, it works?
Can you elaborate on why you think the enter key is involved here, or is that a
hypothesis at this point?
--
You are r
https://bugs.kde.org/show_bug.cgi?id=470432
--- Comment #2 from Matt Keith ---
(In reply to Nate Graham from comment #1)
> Are you saying that at step 4, when you wake up the monitor with the enter
> key, it inappropriately attempts to unlock the screen using an empty
> password?
It does not att
https://bugs.kde.org/show_bug.cgi?id=470432
Nate Graham changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC|
https://bugs.kde.org/show_bug.cgi?id=470432
Ben Bonacci changed:
What|Removed |Added
Product|kde |kscreenlocker
CC|
