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 645782 - Show the password prompt dialog at all times when the screen is locked
Show the password prompt dialog at all times when the screen is locked
Status: RESOLVED DUPLICATE of bug 696330
Product: gnome-screensaver
Classification: Deprecated
Component: dialog
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2011-03-26 20:55 UTC by Jean-François Fortin Tam
Modified: 2014-03-09 17:30 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screencast (678.11 KB, video/ogg)
2011-03-26 20:55 UTC, Jean-François Fortin Tam 		Details

Description Jean-François Fortin Tam 2011-03-26 20:55:21 UTC 
Created attachment 184325 [details]
screencast

Currently, when you resume from suspend and the screen is locked, what you see is a black screen with the username and clock... I don't think users should be expected to see this screen and to guess that they must move the mouse or keyboard to bring up the password prompt dialog.

Basically, the password prompt dialog should probably stay visible at all times (and when power management kicks in, the screen is blanked but that dialog is still there).
Comment 1 Andy Lutomirski 2014-03-08 23:55:04 UTC 
Amen.  The screen with the clock serves no purpose at all except for requiring extra input in order to unlock.

Yes, you can start typing your password from that screen, and it will work on new enough versions of GNOME, *but only if you have exactly one logged-in user*.

Also, training users to type their passwords into things that aren't clearly password prompts is just bad practice.
Comment 2 Matthias Clasen 2014-03-09 17:30:10 UTC 

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