Package Details: fingerprint-gui 1.09-7

Git Clone URL: https://aur.archlinux.org/fingerprint-gui.git (read-only, click to copy)
Package Base: fingerprint-gui
Description: Fingerprint-based authentication, supports UPEK readers with non-free library
Upstream URL: https://github.com/maksbotan/fingerprint-gui
Licenses: GPL
Submitter: ffjia
Maintainer: gborzi
Last Packager: gborzi
Votes: 133
Popularity: 0.54
First Submitted: 2010-08-20 05:55 (UTC)
Last Updated: 2020-08-27 12:52 (UTC)

Latest Comments

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 Next › Last »

ffjia commented on 2010-12-01 05:37 (UTC)

New version updated. For changes and notes, please refer to: CHANGELOG and http://darkblue.homeip.net/fingerprint/Forum/topic.php?TopicId=79&Posts=6 https://launchpad.net/~fingerprint/+archive/fingerprint-gui

ffjia commented on 2010-11-22 06:23 (UTC)

Yep, I use kde, and do not have this issue. I'm not sure whether this issue only exist in gnome or not :( Have you tried the "su username -c "dbus-launch --exit-with-session program"" workaround in arch forum link below?

<deleted-account> commented on 2010-11-19 10:44 (UTC)

@ffjia I would like to confirm that the problem still exists. Login works fine, but su and sudo continue to produce the following error: "GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL)" Don't think it would be helpful, but here is my errors.log: Nov 19 11:59:25 localhost fingerprint-helper[14928]: Started. Nov 19 11:59:33 localhost pam_fingerprint-gui[14927]: ERROR: Prompting for password. Nov 19 11:59:33 localhost sudo[14927]: pam_unix(sudo:auth): conversation failed As for reporting the issue to the fingerprint-gui forum; it has already been reported but with no luck, check out: http://darkblue.homeip.net/fingerprint/Forum/topic.php?TopicId=66&Posts=0 From my understanding you are using kde, could this be the reason you don't have this issue? Is it possible that this issue exists only on gnome?

ffjia commented on 2010-11-16 01:48 (UTC)

@swiftgeek Could you tell me all the details? I can report this issue to the fingerprint-gui forum. Presonnally, I did not have this issue.

swiftgeek commented on 2010-11-14 10:36 (UTC)

still not working ;( "GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL)"

ffjia commented on 2010-10-13 06:42 (UTC)

@R3MU5 It seemed not a fingerprint-gui related issue, same problems reported in Arch forum, please refor to https://bbs.archlinux.org/viewtopic.php?pid=837847

<deleted-account> commented on 2010-10-09 09:05 (UTC)

After upgrading my system on October the 5th, fingerprint-gui has had problems. Login works fine, but su and sudo produce the following error: GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL) Any ideas on how to solve?

ffjia commented on 2010-09-10 01:47 (UTC)

Thanks R3MU5, lol Yep, you have to enroll your fingerprint as root, I simply copy my normal user fingerprint data to /var/lib/fingerprint/root, and change the ownership. I have tested this app on gnome, everything worked fine. As for kde (which is my favorite), the unlock phase does not work with fingerprint, I have to type password. Happy using quad core laptop :)

<deleted-account> commented on 2010-09-09 17:15 (UTC)

I feel like an .....! Sometimes to find the solution, you need to find the "root" of the problem!! Never thought to add fingerprints for root.... su works now as well. :)

<deleted-account> commented on 2010-09-09 16:22 (UTC)

Yes my laptop uses UPEK. The only thing I haven't managed to get to work is su. The changes I made to PAM are the following: For login I edited "gdm" (if you dont use gdm edit whichever login manager you use; xdm, kdm, slim...) and "login". I added to the very top --> "auth sufficient pam_fingerprint-gui.so" and changed "auth required pam_unix.so" to --> "auth required pam_unix.so nullok_secure use_first_pass" I did the same thing for "sudo" and "gnome-screensaver" Now login works with both keyboard and fingerprint reader, as well as sudo and unlock-dialog from gnome-screensaver. Did you manage to get su to work?