After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 786686 - Lock screen likes to expose incorrect passwords
Lock screen likes to expose incorrect passwords
Status: RESOLVED DUPLICATE of bug 758873
Product: gnome-shell
Classification: Core
Component: lock-screen
3.22.x
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-08-23 15:30 UTC by Jan Schmidt
Modified: 2017-08-23 18:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jan Schmidt 2017-08-23 15:30:18 UTC 
If I type an incorrect password in gnome-shell's lock screen and then hit 'Enter' 3 times quickly, it 1) submits the password 2) 2nd Enter pops up the text field context menu 3) 3rd Enter hits the default 'Show Text' option and shows the password just typed

This usually means I end up showing some incorrectly typed variant of my password for some seconds until the field clears, although one time the lock screen then hung with a 'processing' swirly and I couldn't even clear the text field.
Comment 1 Emmanuele Bassi (:ebassi) 2017-08-23 16:34:38 UTC 
If you're typing the password quickly and you have mixed cases, you may be hitting a modifier; this would make this bug a dupe of bug 740043 — but that's supposedly been fixed in GNOME 3.22, so there may be another case not covered by that issue.
Comment 2 Emmanuele Bassi (:ebassi) 2017-08-23 16:35:37 UTC 
Incidentally, I can't reproduce with Shell 3.24.
Comment 3 Jan Schmidt 2017-08-23 17:09:48 UTC 
I can reproduce on 3.22.2, typing only a single lower-case 'a' and then hitting Enter 3 times quickly.
Comment 4 Ray Strode [halfline] 2017-08-23 18:55:20 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the code repository.

*** This bug has been marked as a duplicate of bug 758873 ***