> config? Then your PAM config is what broke it.
Yes, xscreensaver work ok before. I have changed PAM module pam_unix to pam_unix2 to use blowfish passwords.
In /etc/pam.d/common-auth file I change the original file to the new line to enable blowfish passwords:
/etc/pam.d/common-auth.orig: auth required pam_unix.so nullok_secure
to
/etc/pam.d/common-auth: auth required pam_unix2.so nullok debug
If others programs as login (I can login in my machine), passwd (I can change passwords whitout problems), su (I can change user), sudo (I can use it ok) or wdm run whitout problems ... Why xscreensaver don't work ? If my PAM configuration is wrong no program must work.
The PAM configuration for xscreensaver is the default Debian configuration:
[EMAIL PROTECTED]:~$ cat /etc/pam.d/xscreensaver
#
# /etc/pam.d/xscreensaver - PAM behavior for xscreensaver
#
@include common-auth
2006/4/16, Jamie Zawinski <[EMAIL PROTECTED]>:
> Thanks for your answer but I don't think that this error is on my
> configuration or PAM modules.
> Other programs (login, wdm, passwd, sudo, su, etc.) work correctly,
> xscreensaver no.
Did xscreensaver work before you started messing with your PAM
config? Then your PAM config is what broke it.
When you figure out what you did wrong, I'm reasonably certain the
answer will be that you didn't edit pam.d/xscreensaver properly.
I can't tell you what the right thing to put there is in your case,
because I didn't write PAM.
