xscreensaver seems to be having problems with shadow'd passwords. errors in .xsession-errors say xscreensaver-command: xscreensaver window has been deleted. xscreensaver: couldn't get password of "smooge" xscreensaver: couldn't get password of "root" Symptom is that you cant type any password to turn off xscreensaver once it starts up. I have to ALT-F1 and kill it from there. strace indicates a permission denied when the program tries to read /etc/shadow (which I would think is a good thing). However, I thought there would be some sort of PAM thing going on for authentication that doesnt seem to happen (xscreen "forgot" to use PAM?) xscreensaver-3.08-4 pam-0.66-11 couldnt duplicate at work because passwords are in the YP password field.
Downgrading pam to pam-0.66-4 fixed the problem. Something between -4 and -11 is causing xscreensaver to not "work".
using xscreensaver-3.08-4 & pam-0.66-11, xscreensaver prints those error messages on startup, but does lock and unlock the screen correctly (this is in the test lab). What does your /etc/pam.d/xscreensaver say?
*** Bug 2164 has been marked as a duplicate of this bug. *** The update to xscreensaver-2.0.9 in the current build cases the password entry prompt to always fail. To reproduce: lock screen, tap a key, try to enter user's password, it will always fail ------- Additional Comments From notting 04/13/99 10:06 ------- Arrgh. Everyone can duplicate this except me. - are you using shadow passwords (I'm assuming yes) - are you using NIS (I'm assuming no) What version of PAM are you running? It looks like we might have to turn the setuid bit back on.
*** Bug 2164 has been marked as a duplicate of this bug. *** The update to xscreensaver-2.0.9 in the current build cases the password entry prompt to always fail. To reproduce: lock screen, tap a key, try to enter user's password, it will always fail ------- Additional Comments From notting 04/13/99 10:06 ------- Arrgh. Everyone can duplicate this except me. - are you using shadow passwords (I'm assuming yes) - are you using NIS (I'm assuming no) What version of PAM are you running? It looks like we might have to turn the setuid bit back on. ------- Additional Comments From pbrown 04/13/99 16:59 ------- *** This bug has been marked as a duplicate of 2126 ***
This seems to be a bug in /sbin/pwdb_chkpwd, as xscreensaver is properly doing pam authenticate calls.
fixed in some later pwdb release before 6..0