[KLUG Members] Ximian Gnome and Screensavers

[members@kalamazoolinux.org]

>I've been running KDE2 on a SuSe 7.1 box for awhile. Over the weekend I 
>decided to give Ximian Gnome a try so I could see Evolution in action. No 
>problems on the install at all. However, now when I "Lock" the box or the 
>screensaver comes on, I can't get back in. I never had any problems with 
>KDE2 with this, but Ximian doesn't seem to like my password.
>Any thoughts?

Disclaimer: The following ***assumes*** that KDE uses xscreensaver to lock the
screen in the same manner as Ximian GNOME.  If KDE uses it's own screen
saver/locker program then that it probably the issue.  I know nothing at all
about KDE except that is uses Qt (ick) and doesn't really have any component/IPC
mechanism to speak of.

I'd guess that Ximian's xscreensaver RPM stomped on your xscreensaver PAM stack.
 On redhat this is /etc/pam.d/xscreensaver.  This file determines how the
screensaver verfies your password.  We use Kerberos at one site and straight
LDAP at another, and this RPM has done this to us before.  You can simply copy
back the old PAM stack as it should have been backuped up to some other
filename.  If you are using flat file authentication (/etc/passwd) it may have
changed your crypt type (md5, crypt, etc...) or enabled/disabled shadow options
"for" you.

Yes, this is bad RPM behavior.  Config files should never be replaced,  but
installed as blahblah.rpmsomethin if one already exists.  We've complained,  but
it hasn't been fixed yet.




-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/