This has been documented already in bug #22942. However that bug is to upgrade pam and all that is really needed is a one line fix in the sigchld patch. This has also come up on gentoo-user: http://marc.theaimsgroup.com/?l=gentoo-user&m=105854916128781&w=2 and it makes testing the new kernels annoying. Reproducible: Always Steps to Reproduce: 1. Boot any linux-2.6.0-test kernel 2. run xlock or xscreensaver 3. Try to unlock screen Actual Results: You can unlock it. Expected Results: You should be able to unlock it Portage 2.0.49-r2 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1, 2.6.0-test4) ================================================================= System uname: 2.6.0-test4 i686 Pentium III (Coppermine) ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer -falign-functions=4 -mmmx -msse -mfpmath=sse -fforce-addr" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer -falign-functions=4 -mmmx -msse -mfpmath=sse -fforce-addr" DISTDIR="/share/distfiles" FEATURES="sandbox ccache autoaddcvs sandbox,userpriv,fixpackages" GENTOO_MIRRORS="ftp://gentoo.noved.org/ http://gentoo.noved.org/ ftp://ftp.ussg.iu.edu/pub/linux/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 oss avi crypt encode foomaticdb gif jpeg libg++ mad mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib directfb gtkhtml alsa berkdb slang readline tetex aalib bonobo svga ggi tcltk java guile mysql X sdl gpm tcpd pam libwww ssl perl python esd imlib oggvorbis gnome gtk qt motif opengl mozilla cdr acpi apache2 dga dvd evo fbcon flash gd gstreamer gtk2 i8x0 mbox mozaccess mozcalendar mozp3p mozsvg mozxmlterm odbc offensive pcmcia samba sse tiff Xaw3d xosd -3dnow -apm -arts -cups -kde -gdbm"
Just for the record: The same problem occurs with the hardened-sources 2.4.21. It's quite strange ... When I start xlock manually in the shell, I can unlock the screen successfully. When I have xautolock start xlock, I cannot unlock the screen. The only error message I see in the log file is that PAM refused the authentication; enabling debugging in xlock/xlockmore didn't show anything. Alan, the link to the patch that supposedly fixes this doesn't work anymore. Is this patch available somewhere else?
I believe that the link was to this email: http://marc.theaimsgroup.com/?l=linux-kernel&m=104493214921408&w=2 For the record, the problem is with pam-0.75-sigchld. You just need to change SIG_IGN to SIG_DFL on line 21.
is this still an issue?
Now that pam 0.77 is in portage I have not had any problems
I just stopped using xlock, so I can't tell whether the problem is fixed or not. :-) If you want to close the bug, that's fine with me. I'll just re-open it in case I'll experience problems. I shall be re-installing the machine any time soon now anyway, then I'll try xlock again.
this bug was specifically in pam-0.75 which is no longer in portage
