xlock unlocks properly, but xscreensaver 4 won't unlock
Earthlings and SuSians: SYSTEM SuSE 7.3, GNOME. PROBLEM If I manually invoke xlock, I can unlock it. That's good, and expected. If I allow xscreensaver to lock the screen after a timeout, I can't unlock. That is, I get the unlock dialog, but it refuses to accept my password. That's not good, and not expected. WHAT I HAVE DONE, SO FAR In a web search, I found mention that the problem might be due to shadowing. However, in the documented case, xlock did not work until a config change. In my case, xlock *does* perform properly (implying that the necessary config setting is already in place); it's xscreensaver that does not permit unlocking when the timeout lock option has been invoked. I have a /etc/pam.d/xscreensaver file that contains just one line, as follows: "auth required /lib/security/pam_pwdb.so shadow nullok" Can somebody suggest what I should be doing, or what I should be looking for? It's not critical, since I can invoke xlock manually when I leave my workstation, and can recover from it, but it would be darn nice to have a working-and-recoverable lock-out on my xscreensaver... you know... in case I fall asleep.... Thanks for you rimt -- Kevin McLauchlan Chrysalis-ITS, Inc. "Ultimate Trust(TM)"
On Tue, 2002-04-02 at 14:55, Kevin McLauchlan wrote:
If I allow xscreensaver to lock the screen after a timeout, I can't unlock. That is, I get the unlock dialog, but it refuses to accept my password. That's not good, and not expected.
Check the permissions on /usr/X11R6/bin/xscreensaver. Mine looks like this: -rwxr-sr-x 1 root shadow It is important that it's group "shadow", and SGID bit is set (the "s" in the permissions). Some time in the past, I tried to remove that SGID bit. And had a similar problem with locking. What you posted for /etc/pam.d/xscreensaver matches what's on my system. And I know the locking works here. So that's probably not the problem. -- Robert Wohlfarth rjwohlfar@galaxyinternet.net "Is not life more important than food, and the body more important than clothes?" -- Matthew 6:25b
Robert, Thank you, Sir! That was the ticket. Xscreensaver unlocks now, the way it was intended. However, it took effect only after I'd rebooted. There is probably a Linux command that I could/should have issued that would have reset the appropriate bits and pieces in a live system -- i.e., without need to restart. Is that true? /kevin kmclauchlan@chrysalis-its.com On Tue, 2002-04-02 at 22:27, Robert Wohlfarth wrote:
On Tue, 2002-04-02 at 14:55, Kevin McLauchlan wrote:
If I allow xscreensaver to lock the screen after a timeout, I can't unlock. That is, I get the unlock dialog, but it refuses to accept my password. That's not good, and not expected.
Check the permissions on /usr/X11R6/bin/xscreensaver. Mine looks like this: -rwxr-sr-x 1 root shadow
It is important that it's group "shadow", and SGID bit is set (the "s" in the permissions). Some time in the past, I tried to remove that SGID bit. And had a similar problem with locking.
What you posted for /etc/pam.d/xscreensaver matches what's on my system. And I know the locking works here. So that's probably not the problem.
On Wed, 2002-04-03 at 12:34, Kevin McLauchlan wrote:
There is probably a Linux command that I could/should have issued that would have reset the appropriate bits and pieces in a live system -- i.e., without need to restart. Is that true?
These two commands would reset xscreensaver: xscreensaver-command -exit xscreensaver & Also, logging out of X should have done the trick too. The important part is to stop the running process. And restart the program. The restarted version would pick up the new permissions. I'm glad it's working again :) -- Robert Wohlfarth rjwohlfar@galaxyinternet.net "Is not life more important than food, and the body more important than clothes?" -- Matthew 6:25b
participants (2)
-
Kevin McLauchlan -
Robert Wohlfarth