i run: xlock -mode blank and the screen locks. upon trying to enter my password, it says the password is invalid. i try as running as root, and entering roots password. same deal. some handy data: # ldd `which xlock` | egrep 'libcrypt.so|libpam.so' libcrypt.so.1 => /lib/libcrypt.so.1 (0x401c1000) libpam.so.0 => /lib/libpam.so.0 (0x401ef000) $ ldd `which passwd` | egrep 'libcrypt.so|libpam.so' libcrypt.so.1 => /lib/libcrypt.so.1 (0x40027000) libpam.so.0 => /lib/libpam.so.0 (0x40055000) $ /usr/lib/portage/bin/pkglist|grep xlock app-misc/xlockmore-5.03-r4
Tod, You're good at the trickier issues :P
$ xlock -mode blank could not read file "complete.au" could not read file "identify-please.au" could not read file "identify-please.au" could not read file "not-programmed.au" Killed does tha thelp any? the killed is from when i switched to a virtual terminal and killed it, b/c i couldn't get back into x w/o doin gthat
Hi! Could you please provide the following info: 1. the version of sys-libs/pam that you hae installed 2. Is 'pam' in your USE variable?
sorry for the delay, been busy. sys-libs/pam-0.75-r6 pam is in the use variables (make.defaults --- in the portage tree.) checked for a new ebuild, didn't find one.
what's the deal with this? do you need more information?
The deal is I'm very busy and I'll get to it when I can. If you want to expedite the process, a patch attached to this bug report would do the trick.
that's cool --- i just didn't know if the thing had died or something like that. i dont know how to fix it (been busy too) but at some point ill look into it. if you figure anything out, just let me know......
Ok, Please edit your /etc/pam.d/xlock file and change the entry to the following: auth required pam_unix.so nullok Let me know if this works for you and then we can get the fix commited. Thanks for your help.
Ok, Even better edit /etc/pam.d/xlock and use the line auth required /lib/security/pam_stack.so service=system-auth Alternately, you can unpack the xlockmore tarball and cp etc/xlock.pamd /etc/pam.d/xlock I think this is the fix. If you could test I would appreciate it.
perhaps that is the problem --- i have no /etc/pam.d/xlock file...... upon adding that and creating it, the screen unlocks! whee! thanks
alright, the second one works too. if thats the best one, lets go with it.....
Hi! Commited xlockmore-5.03-r5.ebuild which fixes this. Would you mind testing it? The new ebuild will also run xlock without setuid root if 'pam' is in USE.
new version works super.
