Available PAM version in portage is 0.75. PAM 0.77 was released September 23rd 2002.
I cannot handle this, its to big/complex with many patches. The only person I feel comfortable handling this is Azarah -- and Im not certain that we're really 'outdated' because the pam is basically a totally patched up affair. Im afraid Azarah is the authority on this one.
Created attachment 14851 [details, diff] pam-0.77-sigchld.patch Found this on LKML: http://marc.theaimsgroup.com/?l=linux-kernel&m=105838976602659&w=2 Starting with late 2.5.7x kernel, and continuing with 2.6.0-test1, if you lock your screen with xscreensaver, after you try to unlock, xscreensaver hangs. I found that by attaching strace to the process and then quitting, it would continue on normally. It turns out to have something to do with signal handling. In any case, it would be good to get this patch into at least 0.75, because switching VTs to unlock your screen is tiresome. It's a pretty trivial patch, so I can't imagine it would be too hard to apply to 0.75, but I haven't tried.
Created attachment 14973 [details, diff] Corrected sigchld patch from current gentoo patches Upon further inspection, it appears the ebuild is already applying a sigchld patch. The patch saves the SIGCHLD signal handler. However, it sets the handler to SIG_IGN instead of SIG_DFL, which is apparently the correct way. I modified pam-0.75-sigchld.patch from pam-0.75-r11.gentoo.tbz2 to do this, which is attached. It fixes the xscreensaver problem and does not appear to break anything else.
I've been running the above patch for about a week and it works fine.
I've been running this patch for 2 1/2 mo now and it works, plus it is "obviously" correct, i.e. the current signal handling in pam-0.75-r11 is buggy. Azarah, can you give these patches (and their comments) another look?
I just applied the modified sigchld patch and I can confirm now that my xlock works :) thanks!
any work done on 0.77 ?
Yes, http://dev.gentoo.org/~woodchip/pam/.
As described in comment 3, I just tried the following: 1. re-packaged pam-0.75-r11.gentoo.tbz2 by first extracting it and then modifying pam/patchdir/pam-0.75-sigchld.patch.bz2 to replace SIG_IGN with SIG_DFL in 2 places. 2. Put the repackaged pam-0.75-r11.gentoo.tbz2 in /usr/portage/distfiles 3. Updated /usr/portage/sys-libs/pam/files/digest-pam-0.75-r11 to reflect the new size and md5sum for pam-0.75-r11.gentoo.tbz2 4. emerge pam Happy to report that pam-0.75-r11 now let's xlock unlock the screen properly. Running 2.6.0-test10-mm1.
pam-0.77 hit testing recently; I'm merging it today.
In 0.77, as in earlier versions, /etc/security/console.perms contains this line: <dri>=/dev/nvidia* /dev/3dfx* It really ought to be: <dri>=/dev/nvidia* /dev/3dfx* /dev/dri/*
pam-0.77 is now the stable version in Gentoo; maybe this bug can be closed.
Reassigning to base-system for decision on wethever this should be closed or not.
as noted, 0.77 is in portage
