[NTLUG:Discuss] Xscreensaver problem

[Chris Cox]

Alton R. Pouncey, II wrote:
> All,
> 
> I am having issues with xscreensaver and it's driving me nuts.  Here are
> the system particulars:
> 
> Suse 8.2
> kernel 2.4.20-4GB
> Ximian Desktop 2
> Xscreensaver 4.09
> 
> As you can see from the list above, I run Ximian Desktop 2 - I was just
> used to it so I kept using it when I switched to Suse.  When I click on
> the xscreensaver button to lock the desktop, it does not recognize my
> password when I attempt to unlock the desktop.
> 
> As you can guess, this gives me all sorts of fits.  The following errors
> show up in the log:
> 
> xscreensaver: PAM unable to dlopen(/lib/security/pam_stack.so)
> xscreensaver: PAM [dlerror: /lib/security/pam_stack.so: cannot open
> shared object file: No such file or directory]
> xscreensaver: PAM adding faulty module: /lib/security/pam_stack.so

It's possible that the reference to pam_stack is strictly
inside of the /etc/pam.d/xscreensaver file.  So you can probably
tweak that.  The one that comes with SuSE 8.2 simply contains:

auth     required       pam_unix2.so    nullok

pam_stack is a RH-like thing.

You might want to grep through all of the /etc/pam.d and see if
any other files have been twisted to use pam_stack.

See if that fixes things.  Since Ximian is a spawn out of
the RH team... it sort of makes sense that it works better
with RH-like systems.  I'd send the Ximian guys a note if
this fixes things (Ximian desires to be more dist
neutral inspite of their history).