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 603350 - Sometimes correct password is not accepted
Sometimes correct password is not accepted
Status: RESOLVED OBSOLETE
Product: gnome-screensaver
Classification: Deprecated
Component: dialog
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-30 10:47 UTC by Victor Engmark
Modified: 2014-08-20 20:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Debugging output (108.44 KB, text/plain)
2010-01-18 16:24 UTC, Victor Engmark
Details

Description Victor Engmark 2009-11-30 10:47:13 UTC
[reported first at <https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/435928>]

Sometimes, after the computer has been locked for a while (around an hour seems to be the lower limit), I'm unable to dismiss gnome-screensaver with my regular password. I've verified that I'm using the right input mode (USA Dvorak International) by clicking "Leave Message" and typing the password there. I've also changed the input mode to my second option, Norwegian, and typed the password (it's all a-zA-Z0-9 characters). I also verified that I'm able to log in in the first virtual terminal (Ctrl-Alt-F1) with the same password.

This has happened on Ubuntu Netbook Remix 9.04 (with gnome-screensaver 2.24.0-0ubuntu6) and 9.10 (with gnome-screensaver 2.28.0-0ubuntu3) running on an ASUS EEE 900.

Workaround <http://stackoverflow.com/questions/1741067/see-gnome-terminal-output-in-virtual-console>: Ctrl-Alt-F1, login, killall -9 gnome-screensaver.

The last time this happened is a few days ago, so I don't have all the logs anymore. Which files / lines should I include in this report?
Comment 1 Mikel Ward 2009-11-30 23:58:24 UTC
Silly question: are you using sticky keys?  Bug 603427.
Comment 2 Victor Engmark 2009-12-01 09:13:49 UTC
Mikel: No, and I've verified that I can write the password correctly in the "Leave Message" text box.
Comment 3 Victor Engmark 2010-01-18 16:24:27 UTC
Created attachment 151681 [details]
Debugging output

Gathered with the following command:
gnome-screensaver --no-daemon --debug > /tmp/gs.log 2>&1 &
Comment 4 William Jon McCann 2010-01-29 02:50:23 UTC
Yeah looks like your authentication is failing.  Something in your PAM stack has a timeout or cookie or something.

Can you turn off your screenlock, wait the same amount of time, then try using the test-passwd tool that is in the gnome-screensaver sources?  That will help peek into what PAM is doing.

Thanks.
Comment 5 Victor Engmark 2010-02-02 10:48:46 UTC
(In reply to comment #4)
> Can you turn off your screenlock, wait the same amount of time, then try using
> the test-passwd tool that is in the gnome-screensaver sources?  That will help
> peek into what PAM is doing.

Could you please provide some command line to do this, and the name of the Ubuntu package (if any)? I'm not familiar with test-passwd.

Also, is there some way I could verify my gnome-screensaver installation, as hinted in <http://live.gnome.org/GnomeScreensaver/FrequentlyAskedQuestions#Why_does_the_screensaver_unlock_dialog_always_think_my_password_is_invalid.3F>?
Comment 6 Tobias Mueller 2010-06-10 09:27:04 UTC
William, can you address the questions raised by the reporter in comment #5?
Comment 7 Bastien Nocera 2014-08-20 20:23:43 UTC
The screen lock is now implemented directly in gnome-shell, not in
gnome-screensaver (as it was with older version of GNOME 3 and GNOME 2.x).

If the reported problems persists in recent versions of GNOME, please file a new bug against gnome-shell with the "lock-screen" component selected.

If your installation is an older version of GNOME that cannot be upgraded (such as an enterprise version), please use the appropriate support mechanism from your vendor, or your distribution instead.