problem unlocking screensaver
 

Hi all,

I am having a problem unlocking the screensaver. When I type in the password, it just sits there and does nothing. I end up having to kill the process in order to get it unlocked. Has anyone run into this problem as well? I have found other messages about this elsewhere, but no one seems to have a solution.
I also do have a few settings that may be a little different. I am running SuSE 8.1 with KDE 3.0. I am using kerberos to authenticate against the Active Directory. I don't know if this may be the problem. Our LDAP server may be a bit slow and the screensaver may just be timing out before it gets a response from the server, but I do not know.

Any help would be much appreciated!

Thanks.

Ok, I'm sure it has something to do with the Kerberos - AD communication. Whenever I take out the AD authentication, everything works fine...the screensaver unlocks like it should. I have checked the logs and there are no errors...the screensaver just seems to timeout and not wait for any response from the AD. There must be some timeout somewhere that I need to change...maybe in kcheckpass or something, but I haven't had any luck.

Here is a weird bit of info as well:
I have another desktop (Ctrl+Alt+F2) running tail -f /var/log/messages so that I can debug this problem. The interesting part is that when I am in the GUI and I type in the password to unlock the desktop, I quickly switch to this desktop to watch the logs and curious enough, the dekstop will unlock after about 10 seconds. If I don't do this...and I stay in the GUI while I am trying to unlock it, nothing will happen...it will just stay locked. It works every time. I can show you the logs if you are interested.

It looks like it comes from the GUI settings:rolleyes:
that is to say the parent application

What kind of settings do you mean? I've been going through the KControl to see if something might be of relevance there, but I can't find anything.

I'm a newbie it is just a suggestion...
i don't know have a look in the screen saver preferences too
or in /etc/....
lots of config files there
see the KDE options i can't help you further

The solution turned out to be a timeout issue. Our resolv.conf was wrong, and therefore the request through DNS to the AD was taking too long, and the service for the screensaver timed out. I fixed resolv.conf and this fixed the problem. Thanks!

I've a similar problem.
gnome-screensaver is not unlocking for AD accounts viz. 'domain\xxxxx'. Even after entering correct password, system remains locked. Could not find identify the changes to be done in resolv.conf

Output of /var/log/secure (Failure case):
gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390)
gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password
gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'domain\xxxxx' granted access

It works fine for local accounts.
Output of /var/log/secure:
gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): getting password (0x00000390)
gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): pam_get_item returned a password
gnome-screensaver-dialog: pam_winbind(gnome-screensaver:auth): user 'abcde' granted access
gnome-screensaver-dialog: pam_winbind(gnome-screensaver:account): user 'abcde'granted access

/etc/pam.d/gnome-screensaver
#%PAM-1.0

# Fedora Core
auth include system-auth
account include system-auth
password include system-auth
session include system-auth

# SuSE/Novell
#auth include common-auth
#account include common-account
#password include common-password
#session include common-session

Environment:
RHEL 5.7
gnome-screensaver-2.16.1-8.el5_7.4

Kindly suggest if any settings needs to be changed.

Thanks.