xlock from xlockmore 5.08.2 will not unlock the screen when run as a normal user. It is built against PAM (checked with ldd), as it should have been. If I strace it, I see it open the pam files (xlock, system-auth, approprate modules) and then try to open /etc/passwd and /etc/shadow. Opening /etc/shadow fails when xlock is not running as root. This obviously makes xlock almost entirely useless. :) emerge info: Portage 2.0.50_pre16 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r3, 2.6.0-test10-m m1) ================================================================= System uname: 2.6.0-test10-mm1 i686 Intel(R) Pentium(R) M processor 1000MHz Gentoo Base System version 1.4.3.10 Autoconf: sys-devel/autoconf-2.57-r1 Automake: sys-devel/automake-1.7.5-r2 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1 /share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -march=pentium3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://gentoo.noved.org/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib acpi alsa apm arts avi berkdb cdr cjk crypt cscope cups doc dvd ema cs encode esd ethereal foomaticdb gdbm ggi gif gnome gphoto2 gpm gps gtk gtk2 gt khtml imlib java joystick jpeg kde ldap leim libg++ libwww mad maildir mbox mikm od mmx motif mozilla mpeg mysql ncurses nls nocd oggvorbis opengl oss pam pcmcia pda pdflib perl png pnp python qt quicktime readline ruby samba scanner sdl sla ng slp snmp spell sse ssl svga tcpd truetype unicode usb videos wavelan x86 xml2 xmms xv zlib"
Could you please do me a favor and pursue this upstream? It is our policy for the developer (me) to do this, but I am admittedly busy, and you clearly have above average bug hunting skills. If the temporary solution, or a version bump provides the fix, please reopen and notify me here. TIA :)
I'm not having this problem with Xlockmore 5.11.1.