Gnome-screensaver Does not accept a password and unlock

[Ian Santopietro]

If the screen is locked, and Gnome-screensaver activates and locks the screen, then it will not accept the user's password for unlock. Instead, it will simply reject it as if it were correct. The password is good, and caps/numlock are not active.

As a workaround, one can switch to a virtual terminal (Ctrl+Alt+F1), login, then run:

export DISPLAY=:0.0
gnome-screensaver-command -d

Then switch back to the X session and the screen will be unlocked.

[Ian Santopietro (isantop)]

Believed to be caused by bad configuration. Attempting to replace the default wallpaper as a workaround.

[Ian Santopietro (isantop)]

Workaround has worked. I think I have a (hackish) way to apply the fixed bits. It basically involves keeping the default background, but replacing it with a totally black image. This is not anywhere near what I would call "Fixed", but since no one seems to be able to document how to change the configuration, this will have to do.

[Maarten L. Hekkelman (hekkel)]

Same here.

If this happens, you can choose 'switch user' and then login again using the normal GDM login screen. So it is the screen saver dialog that does not recognise the password. auth.log says:

May 6 11:27:43 lord-jim unix_chkpwd[8053]: check pass; user unknown
May 6 11:27:44 lord-jim unix_chkpwd[8055]: check pass; user unknown
May 6 11:27:44 lord-jim unix_chkpwd[8055]: password check failed for user (maarten)
May 6 11:27:44 lord-jim gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=maarten
...
May 6 11:33:17 lord-jim gdm-session-worker[8300]: pam_succeed_if(gdm:auth): requirement "user ingroup nopasswdlogin" not met by user "maarten"
May 6 11:33:19 lord-jim gdm-session-worker[8300]: pam_unix(gdm:session): session opened for user maarten by (uid=0)
May 6 11:33:19 lord-jim gdm-session-worker[8300]: pam_ck_connector(gdm:session): nox11 mode, ignoring PAM_TTY :1

[Ian Santopietro (isantop)]

This is a bug with OxygenOS. It's not applicable to Ubuntu in General.