possibly messed-up permissions from GLOcean

[Jason 'vanRijn' Kasper]

On Thursday 03 February 2005 20:53, s s wrote:
> > Everything SEEMS to be acting fine now...
>
> ...But not anymore. If I lock the desktop in KDE, I
> cannot unlock it. It doesn't recognize my password.
> so...
> the permissions for kdesktop_lock still seem to be
> broken. I don't know exactly what they should be,
> maybe there is a file in /opt/kde/bin that it needs to
> Write to?
> Does anyone out there know?
>

I don't know how you got where you are with this (self-installed packages, 
etc.) but 2 things that I've had to learn the hard way recently are as 
follows:

- $KDEDIR/bin/kcheckpass needs to be owned by root and SUID
- /etc/pam.d/kde needs to be correct (like this...)

#%PAM-1.0
auth       required     pam_stack.so service=system-auth
auth       required     pam_nologin.so
auth       sufficient   pam_timestamp.so
account    required     pam_stack.so service=system-auth
password   required     pam_stack.so service=system-auth
session    required     pam_stack.so service=system-auth
session    optional     pam_timestamp.so
session    optional     pam_selinux.so
session    optional     pam_c

Hope this helps!!  =:)

-- 

,-----------------------------------------------------------------//
| Jason 'vanRijn' Kasper ::  Numbers 6:22-26 
 `
 | All brontosauruses are thin at one end, much MUCH thicker 
 | in the middle, and then thin again at the far end.  That is 
 | the theory that I have and which is mine, and what it is too.  
 ,
| bash$ :(){ :|:&};:
`----------------------//
___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.