Re: [arch-general] Unlocking the screen through fprintd

2016-10-20 Thread Bennett Piater
> Not using fprint, but merely an idea (you have possibly already checked > that): maybe the PAM-file for the screenlocker has a higher priority for > passwords than for the fingerprint sensor while the rest has it the > other way around. > > iirc this depends on the ordering of the corresponding

Re: [arch-general] Unlocking the screen through fprintd

2016-10-20 Thread Jonas Große Sundrup
Am 20.10.2016 um 10:13 schrieb Bennett Piater: > However, every screen locker I have tried that supports PAM at all > (i3lock, xlockmore, xscreensaver, kscreenlocker) all ask for my > fingerprint AFTER I typed in my password. Not using fprint, but merely an idea (you have possibly already checked

Re: [arch-general] Unlocking the screen through fprintd

2016-10-20 Thread Bennett Piater
> Unfortunately I can't help you, I'm just curious. Well, you did anyway! > If you type no password at all, just push enter, does the fingerprint > check allow you to unlock the screen? Or doesn't it appear, if you just > push enter without typing a password? I tested it with kscreenlocker and

Re: [arch-general] Unlocking the screen through fprintd

2016-10-20 Thread Ralf Mardorf
On Thu, 20 Oct 2016 10:13:59 +0200, Bennett Piater wrote: >However, every screen locker I have tried that supports PAM at all >(i3lock, xlockmore, xscreensaver, kscreenlocker) all ask for my >fingerprint AFTER I typed in my password. Unfortunately I can't help you, I'm just curious. If you type

[arch-general] Unlocking the screen through fprintd

2016-10-20 Thread Bennett Piater
Hi all, I have been trying to get fprint working properly with screen lockers for months and have yet to find a working solution. I am using i3wm without DM. Login on the TTY and sudo work properly: They ask me to swipe the finger and then ask for my password if that didn't work. However, every