[KLUG Members] Ximian Gnome and Screensavers
Doc Rea
members@kalamazoolinux.org
Sun, 03 Mar 2002 15:59:25 -0500
--=====================_63897269==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed
I just wanted to provide an update. I did try this, but it didn't do the
trick. So, I started playing around....Needless to say, I am not skilled in
the ways of Gnome and messed up more than I fixed, but I sure learned a lot ;}
Luckily, I always try new stuff on one system that I can sacrifice to the
Linux gods. This was one of them. It's back happily running SuSe 7.3 and KDE2.
Later...
At 11:02 AM 2/26/2002 -0500, you wrote:
> >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/
>_______________________________________________
>Members mailing list
>Members@kalamazoolinux.org
>
--=====================_63897269==_.ALT
Content-Type: text/html; charset="us-ascii"
<html>
<font size=3>I just wanted to provide an update. I did try this, but it
didn't do the trick. So, I started playing around....Needless to say, I
am not skilled in the ways of Gnome and messed up more than I fixed, but
I sure learned a lot ;}<br><br>
Luckily, I always try new stuff on one system that I can sacrifice to the
Linux gods. This was one of them. It's back happily running SuSe 7.3 and
KDE2.<br><br>
Later...<br><br>
At 11:02 AM 2/26/2002 -0500, you wrote:<br>
<blockquote type=cite class=cite cite>>I've been running KDE2 on a
SuSe 7.1 box for awhile. Over the weekend I <br>
>decided to give Ximian Gnome a try so I could see Evolution in
action. No <br>
>problems on the install at all. However, now when I "Lock"
the box or the <br>
>screensaver comes on, I can't get back in. I never had any problems
with <br>
>KDE2 with this, but Ximian doesn't seem to like my password.<br>
>Any thoughts?<br><br>
Disclaimer: The following ***assumes*** that KDE uses xscreensaver to
lock the<br>
screen in the same manner as Ximian GNOME. If KDE uses it's own
screen<br>
saver/locker program then that it probably the issue. I know
nothing at all<br>
about KDE except that is uses Qt (ick) and doesn't really have any
component/IPC<br>
mechanism to speak of.<br><br>
I'd guess that Ximian's xscreensaver RPM stomped on your xscreensaver PAM
stack.<br>
On redhat this is /etc/pam.d/xscreensaver. This file
determines how the<br>
screensaver verfies your password. We use Kerberos at one site and
straight<br>
LDAP at another, and this RPM has done this to us before. You can
simply copy<br>
back the old PAM stack as it should have been backuped up to some
other<br>
filename. If you are using flat file authentication (/etc/passwd)
it may have<br>
changed your crypt type (md5, crypt, etc...) or enabled/disabled shadow
options<br>
"for" you.<br><br>
Yes, this is bad RPM behavior. Config files should never be
replaced, but<br>
installed as blahblah.rpmsomethin if one already exists. We've
complained, but<br>
it hasn't been fixed yet.<br><br>
<br><br>
<br>
-------------------------------------------------<br>
This mail sent through IMP:
<a href="http://horde.org/imp/" eudora="autourl">http://horde.org/imp/</a><br>
_______________________________________________<br>
Members mailing list<br>
Members@kalamazoolinux.org<br>
<a href="" eudora="autourl"></a></font></blockquote></html>
--=====================_63897269==_.ALT--