This is getting a little bit enoying...
After I 'succesfully' update SuSE from 9.0 to 9.1 I was left with a screensaver issue.
Once the screensaver comes up I can get back into my session, password is not accepted.
Tried to change my passwd, played with powersafe options, tried to take away
the requirement for the password etc etc NO LUCK
In the KDE config the 'password required' box is not tagged.
Yesterday when the screensaver came up I still had to give a password (which fails)
Today however -without changing a thing in the conf- when the screensaver kicks in
KDE is simply killed and I have to login again...
Reminds me to Micro$hit stuff... anybody got a clue what is going on?
I have the latest SuSE patches installed.
In messages I found this :
Jul 15 08:11:49 unpocoloco kdm[3841]: X server for display :0 terminated unexpectedly
Jul 15 08:11:49 unpocoloco kdm: :0[4575]: pam_unix2: session finished for user pwildenb, service xdm
Jul 15 08:12:42 unpocoloco kdm: :0[4766]: pam_unix2: session started for user pwildenb, service xdm
Jul 15 08:13:03 unpocoloco gconfd (pwildenb-4939): starting (version 2.4.0.1), pid 4939 user 'pwildenb'
Now this pam_ thingie worries me a bit, I never used/configured pam AFAIK. Is this something 'new' in SuSE 9.1 ?
Digging a bit more : /etc/pam.d> more xscreensaver #%PAM-1.0 auth required pam_unix2.so nullok
This should do a check against whatever pw is in the shadow file, no?
When is the xlock file in /etc/pam.d used, the content is the same as xscreensaver?
And finally should it not read something like : password required pam_unix2.so nullok use_first_pass use_authtok
Thanks
Peter
_______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
