[OpenAFS] xscreensaver locks at 2nd try to unlock

[Marc Schmitt]

Hi again,

Running xscreensaver in verbose mode, I got the following log:
-----------------------------------------------------------------
xscreensaver: warning: $DISPLAY is not set: defaulting to ":0.0".
xscreensaver 3.33, copyright (c) 1991-2001 by Jamie Zawinski <jwz@jwz.org>.
xscreensaver: running as userx/groupy (x/y)
xscreensaver: in process 2635.
xscreensaver: xscreensaver-gl-helper says the GL visual is 0x21 (the 
default).
xscreensaver: running on display ":0.0"
xscreensaver: vendor is The XFree86 Project, Inc, 4003
xscreensaver: useful extensions:
xscreensaver:  MIT Screen-Saver
xscreensaver:  Shared Memory
xscreensaver:  Double-Buffering
xscreensaver:  Power Management
xscreensaver:  GLX
xscreensaver:  XF86 Video-Mode
xscreensaver: screen 0 non-mapped depths: 24
xscreensaver: not using server's lame MIT-SCREEN-SAVER extension.
xscreensaver: consulting /proc/interrupts for keyboard activity.
xscreensaver: using default visual 0x21 (TrueColor,   depth: 24, cmap: 
default)
xscreensaver: saver window is 0xc00001.
xscreensaver: selecting events on extant windows... done.
xscreensaver: LOCK ClientMessage received; activating and locking.
xscreensaver: locked mode switching.
xscreensaver: blanking screen at Mon Nov 26 11:12:13 2001.
xscreensaver: grabbing keyboard on 0x58... GrabSuccess.
xscreensaver: grabbing mouse on 0x58... GrabSuccess.
xscreensaver: fading...
xscreensaver: fading done.
xscreensaver: switching to visual 0x21 (TrueColor,   depth: 24, cmap: 256)
xscreensaver: saver window is 0xc00006.
xscreensaver: destroyed old saver window 0xc00001.
xscreensaver: suspending pid 2639.
xscreensaver: prompting for password.
xscreensaver: child pid 2639 (penetrate) stopped with SIGSTOP.
xscreensaver: grabbing server...
xscreensaver: ungrabbing mouse (was 0x58).
xscreensaver: grabbing mouse on 0xc0000c... GrabSuccess.
xscreensaver: ungrabbing server.
xscreensaver: pam_start ("xscreensaver", "userx", ...) ==> 0 (Success)
xscreensaver:   pam_set_item (p, PAM_TTY, ":0.0") ==> 0 (Success)
xscreensaver:     PAM ECHO_OFF("AFS Password: ") ==> password
xscreensaver:   pam_authenticate (...) ==> 0 (Success)
xscreensaver:   pam_setcred (...) ==> 0 (Success)
xscreensaver: pam_end (...) ==> 0 (Success)
xscreensaver: password correct.
xscreensaver: grabbing server...
xscreensaver: ungrabbing mouse (was 0xc0000c).
xscreensaver: grabbing mouse on 0x58... GrabSuccess.
xscreensaver: ungrabbing server.
xscreensaver: resuming pid 2639.
xscreensaver: unblanking screen at Mon Nov 26 11:12:19 2001.
xscreensaver: killing pid 2639.
xscreensaver: child pid 2639 (penetrate) terminated with SIGTERM.
xscreensaver: ungrabbing mouse (was 0x58).
xscreensaver: ungrabbing keyboard (was 0x58).
xscreensaver: unlocked mode switching.
xscreensaver: awaiting idleness.
xscreensaver: LOCK ClientMessage received; activating and locking.
xscreensaver: locked mode switching.
xscreensaver: blanking screen at Mon Nov 26 11:12:27 2001.
xscreensaver: grabbing keyboard on 0x58... GrabSuccess.
xscreensaver: grabbing mouse on 0x58... GrabSuccess.
xscreensaver: fading...
xscreensaver: fading done.
xscreensaver: spawning "shadebobs -root" in pid 2643.
xscreensaver: suspending pid 2643.
xscreensaver: prompting for password.
xscreensaver: grabbing server...
xscreensaver: ungrabbing mouse (was 0x58).
xscreensaver: grabbing mouse on 0xc00083... GrabSuccess.
xscreensaver: ungrabbing server.
xscreensaver: child pid 2643 (shadebobs) stopped with SIGSTOP.
xscreensaver: pam_start ("xscreensaver", "userx", ...) ==> 0 (Success)
xscreensaver:   pam_set_item (p, PAM_TTY, ":0.0") ==> 0 (Success)
xscreensaver:     PAM ECHO_OFF("AFS Password: ") ==> password
xscreensaver:   pam_authenticate (...) ==> 0 (Success)
-------------------------------------------------------------

There it hangs, obviously pam_setcred() and pam_end() are not executed 
the second time I try to unlock, the screensaver waits forever.

On http://www.tu-chemnitz.de/urz/afs/afs_pam.html, it says that 
set_token should only be used if the application does NOT call 
pam_setcred(), I took it out of system-auth, but it didn`t change 
anything. Any hints welcome. Thanks.

Regards,
	Marc