I am running Feisty up to date and cannot log back in after locking the screen, although logging in as a new user works. Killing gnome-screensaver works as a work-around.
/var/log/auth.log says:
Mar 29 22:42:54 new unix_chkpwd[9765]: check pass; user unknown
Mar 29 22:42:54 new gnome-screensaver-dialog: (pam_unix) authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=dahen
Mar 29 22:43:59 new gnome-screensaver-dialog: (pam_unix) auth could not identify password for [dahen]
cat /etc/pam.d/common-auth
#
# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
auth required pam_unix.so nullok_secure
I am running Feisty up to date and cannot log back in after locking the screen, although logging in as a new user works. Killing gnome-screensaver works as a work-around.
/var/log/auth.log says: er-dialog: (pam_unix) authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=dahen er-dialog: (pam_unix) auth could not identify password for [dahen]
Mar 29 22:42:54 new unix_chkpwd[9765]: check pass; user unknown
Mar 29 22:42:54 new gnome-screensav
Mar 29 22:43:59 new gnome-screensav
cat /etc/pam. d/gnome- screensaver
@include common-auth
cat /etc/pam. d/common- auth d/common- auth - authentication settings common to all services
#
# /etc/pam.
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
auth required pam_unix.so nullok_secure