I have an annoying issue where after following good practise of logging into SLES as a non-root user the gnome screensaver fails to unlock. Our work around is to switch to runlevel 3 then back to 5 or kill X with CRTL-ALT-BACKSPACE.
The server is question isSUSE Linux Enterprise Server 10 (i586) SP2 and
OES 2 SP1.
Strangely /var/log/messages shows multiple attempts by root and my account (paulr) when I attempt just one unlock.
May 4 08:12:07 fileserver unix2_chkpwd[20055]: pam_authenticate(gnome-screensaver, paulr): Authentication failure
May 4 08:12:12 fileserver unix2_chkpwd[20058]: pam_authenticate(gnome-screensaver, root): Authentication failure
May 4 08:12:12 fileserver unix2_chkpwd[20067]: pam_authenticate(gnome-screensaver, paulr): Authentication failure
May 4 08:12:17 fileserver unix2_chkpwd[20070]: pam_authenticate(gnome-screensaver, root): Authentication failure
May 4 08:12:17 fileserver unix2_chkpwd[20078]: pam_authenticate(gnome-screensaver, paulr): Authentication failure
PAM's gnome-screensaver has not been modified to my knowledge.
Can anyone confirm this by comparing their SLES 10 box to mine below?
fileserver:/etc/pam.d # cat gnome-screensaver
#%PAM-1.0
# Fedora Core
#auth include system-auth
#account include system-auth
#password include system-auth
#session include system-auth
# SuSE/Novell
auth include common-auth
account include common-account
password include common-password
session include common-session
Regards
Paul
Gnome Screensaver fails to unlock
Threaded Mode
