Package Details: fingerprint-gui 1.09-1

Git Clone URL: https://aur.archlinux.org/fingerprint-gui.git (read-only)
Package Base: fingerprint-gui
Description: Application for fingerprint-based authentication, automatically support UPEK fingerprint readers with non-free library
Upstream URL: http://www.ullrich-online.cc/fingerprint/
Licenses: GPL
Submitter: ffjia
Maintainer: arcanis
Last Packager: arcanis
Votes: 98
Popularity: 1.616078
First Submitted: 2010-08-20 05:55
Last Updated: 2016-08-04 18:11

Latest Comments

stormridertx commented on 2016-08-04 16:45

The download link has changed:
http://www.ullrich-online.cc/fingerprint/download/fingerprint-gui-1.08.tar.gz

Also, it looks like 1.09 was just released.

ffjia commented on 2013-07-17 05:04

Thanks, I did not notice that the link not work any more. Package updated.

bradpitcher commented on 2013-07-16 16:59

OK, I see the problem. The download link in the PKGBUILD points to an html file, which works in the browser because the html has frames, but doesn't work with wget. Inspecting the source, you can find the real link:
http://ullrich-online.cc/nview/Appliance/fingerprint/download/fingerprint-gui-1.05.tar.gz

Change the first link in source in the PKGBUILD to
http://ullrich-online.cc/nview/Appliance/fingerprint/download/${pkgname}-${pkgver}.tar.gz

and it works! The existing md5 sum matches. Now I just need to figure out how to use the program.

deathangel908 commented on 2013-07-14 17:51

Help me with installing package.
First time it failed with md5 summ. When I generated md5 and corrected the PKGBUILD file, the build failed with "no file or directory in" "cd ${srcdir}/${pkgname}-${pkgver} " PKGBUILD line on build section. I tried to create the dir, or change the current directory up level, but still packer echoes this:

==> Starting build()...
Usage: qmake-qt4 [mode] [options] [files]
...
...
==> ERROR: A failure occurred in build().
Aborting...
The build failed.
-------------------
How should build section look like?

build() {
cd ${srcdir}/${pkgname}-${pkgver}
#set -x
# Use new animated image created by Anton Krug
tar xf ../finger-swipe-animation.tar
qmake-qt4 PREFIX=/usr LIB=/usr/lib LIBPOLKIT_QT=LIBPOLKIT_QT_1_1 || return 1
make
}

deathangel908 commented on 2013-07-14 17:51

Help me with installing package.
First time it failed with md5 summ. When I generated md5 and corrected the PKGBUILD file, the build failed with "no file or directory in" "cd ${srcdir}/${pkgname}-${pkgver} " PKGBUILD line on build section. I tried to create the dir, or change the current directory up level, but still packer echoes this:

==> Starting build()...
Usage: qmake-qt4 [mode] [options] [files]
...
...
==> ERROR: A failure occurred in build().
Aborting...
The build failed.
-------------------
How should build section look like?

build() {
cd ${srcdir}/${pkgname}-${pkgver}
#set -x
# Use new animated image created by Anton Krug
tar xf ../finger-swipe-animation.tar
qmake-qt4 PREFIX=/usr LIB=/usr/lib LIBPOLKIT_QT=LIBPOLKIT_QT_1_1 || return 1
make
}

deathangel908 commented on 2013-07-14 17:51

Help me with installing package.
First time it failed with md5 summ. When I generated md5 and corrected the PKGBUILD file, the build failed with "no file or directory in" "cd ${srcdir}/${pkgname}-${pkgver} " PKGBUILD line on build section. I tried to create the dir, or change the current directory up level, but still packer echoes this:

==> Starting build()...
Usage: qmake-qt4 [mode] [options] [files]
...
...
==> ERROR: A failure occurred in build().
Aborting...
The build failed.
-------------------
How should build section look like?

build() {
cd ${srcdir}/${pkgname}-${pkgver}
#set -x
# Use new animated image created by Anton Krug
tar xf ../finger-swipe-animation.tar
qmake-qt4 PREFIX=/usr LIB=/usr/lib LIBPOLKIT_QT=LIBPOLKIT_QT_1_1 || return 1
make
}

deathangel908 commented on 2013-07-14 17:40

Help me with installing package.
First time it failed with md5 summ. When I generated md5 and corrected the PKGBUILD file, the build failed with "no file or directory in" "cd ${srcdir}/${pkgname}-${pkgver} " PKGBUILD line on build section. I tried to create the dir, or change the current directory up level, but still packer echoes this:

==> Starting build()...
Usage: qmake-qt4 [mode] [options] [files]
...
...
==> ERROR: A failure occurred in build().
Aborting...
The build failed.

deathangel908 commented on 2013-07-14 17:38

Help me with installing package.
First time it failed with md5 summ. When I generated md5 and corrected the PKGBUILD file, the build failed with "no file or directory in" "cd ${srcdir}/${pkgname}-${pkgver} " PKGBUILD line on build section. I tried to create the dir, or change the current directory up level, but still packer echoes this:

==> Starting build()...
Usage: qmake-qt4 [mode] [options] [files]
...
...
==> ERROR: A failure occurred in build().
Aborting...
The build failed.

ffjia commented on 2013-05-15 02:19

@haagch - I added "-j1" switch to make. Hope that you all can install this package successfully.

haagch commented on 2013-05-14 14:43

Should be "make -j1 INSTALL_ROOT=${pkgdir}/ install" in package(). Doesn't really work with more jobs.

nickoe commented on 2013-03-30 12:01

dkasak@ please delete your comment, it has been fixed.

dkasak commented on 2013-03-22 10:06

This package is still broken due to calling qmake4 instead of qmake-qt4. There is no qmake4 anymore (pacman -Ql qt4 and see for yourself).

lockheed commented on 2013-03-19 10:58

I can't get around that:

-> Downloading BSAPI_4.3.291Lite_SDK_for_Linux.tar.gz...
--2013-03-19 11:57:32-- http://volker.de/wp-content/uploads/2012/12/BSAPI_4.3.291Lite_SDK_for_Linux.tar.gz
Resolving volker.de (volker.de)... 95.143.172.115
Connecting to volker.de (volker.de)|95.143.172.115|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
2013-03-19 11:57:32 ERROR 403: Forbidden.

==> ERROR: Failure while downloading BSAPI_4.3.291Lite_SDK_for_Linux.tar.gz
Aborting...
==> ERROR: Makepkg was unable to build fingerprint-gui.

teateawhy commented on 2013-03-17 18:31

Please replace "qmake4" in line 45 with "qmake-qt4" . Thank you.

ffjia commented on 2013-03-14 08:38

@Gordin - Do you mind to upgrade to the latest qt package? Please refer to this: https://www.archlinux.org/news/qt4-replaces-qt/

What kind of cpu do you use? What's the `MAKEFLAGS' of your /etc/makepkg.conf file? The output of `nproc' please?

Anyone else has this `-j1' issue?

Gordin commented on 2013-03-14 06:53

also, the
make INSTALL_ROOT=${pkgdir}/ install
needs a -j1
(Am I the only one who needs the -j1 there? If I don't specify it there packaging the PKGBUILD fails every time. the actual compiling works fine with multiple threads, just the make install fails on my machine)

Gordin commented on 2013-03-14 06:46

Comment by swiftgeek
2013-03-02 05:45
s/qmake4/qmake-qt4/

ffjia commented on 2013-03-14 03:06

@go2sh - why did you flag this outdated?

swiftgeek commented on 2013-03-04 17:36

official repos are indeed providing only `qmake-qt4`
https://www.archlinux.org/packages/extra/x86_64/qt4/files/

swiftgeek commented on 2013-03-04 17:31

official repos are indeed providing only `qmake-qt4`

ffjia commented on 2013-03-04 04:27

@jakob - well, maybe that means you have not upgraded your qt package for a while. It looks like I need to update the qt version in makedepends.

jakob commented on 2013-03-03 11:05

@ffjia: I only've got /usr/bin/qmake-qt4 which is a symlink to /usr/lib/qmake and build fails with your PKGBUILD. Substituting "qmake4" by "qmake-qt4" in line 45 however makes it build fine…

jakob commented on 2013-03-03 11:02

@ffjia: I only've got /usr/bin/qmake-qt4 which is a symlink to /usr/lib/qmake and build fails with your PKGBUILD. Substituting "qmake4" by "qmake-qt4" in line 45 however makes it build fine…

ffjia commented on 2013-03-02 13:49

@swiftgeek - I only have "qmake4" in my system, after replacing `qt' with `qt4'. Also you could refer to this: https://mailman.archlinux.org/pipermail/arch-dev-public/2013-February/024537.html

swiftgeek commented on 2013-03-02 05:45

s/qmake4/qmake-qt4/

ffjia commented on 2013-03-02 02:29

* Only copy libbsapi.so of BSAPI 4.3.29 when `lsusb -d 147e:2020`
* Update makedepends array due to the replacing of qt with qt4

ffjia commented on 2013-02-27 06:29

@all - thanks for the feedback

@ macman31- good idea, I'll give it a try

Anonymous comment on 2013-02-25 17:47

@ffjia - I'm happy to help. My laptop is a Bonobo Extreme from System76, based on a Clevo P370EM.
Maybe you can put an "if" in the PKGBUILD to copy the libbsapi.so libraries from BSAPI_4.3.291Lite_SDK_for_Linux only if a 147e:2020 Upek sensor is detected ?

jacook commented on 2013-02-25 17:38

My version (with Upek 147e:1002) works again after the latest update. Thank you!!

arcanis commented on 2013-02-25 13:11

@ffjia
maybe. Unfortunately, I can't remember exactly what I did.

arcanis commented on 2013-02-25 13:10

@ffjia
'plugdev' group is removed (and created again) in "post_upgrade" function too. I don't know why it is needed, but it is exists:
post_upgrade() {
ldconfig
cat << EOF
....
if [[ `lsusb -d 0483:` ]] || [[ `lsusb -d 147e:` ]]
then
getent group plugdev &> /dev/null || groupadd -r plugdev > /dev/null
chown -R root.plugdev /var/upek_data
chown root.plugdev /etc/upek.cfg
fi
}

post_remove() {

ffjia commented on 2013-02-25 10:56

@macman31 - thanks dude, it's very kind of you to show us how to find the root cause of this issue. I'm not sure if my sensor has EEPROM or not, my laptop is Lenovo T410s. What's your model?

@arcanis - The `post_remove()' will remove the `plugdev' group, maybe you uninstalled this package before upgrading it?

For those who have 147e:2020 Upek sensor, you could install the `libbsapi.so' manually, please refer to:

http://askubuntu.com/questions/193528/how-to-enable-fingerprint-device-for-thinkpad-t430s-in-12-04/236793#236793

and

http://volker.de/2012/12/fingerprint-gui-und-das-thinkpad-t430s/

arcanis commented on 2013-02-25 00:00

Hmm, but аfter removal of the patch, ше works in tty and for su. So..I don't know. Finally, it thing works do not touch it %)

arcanis commented on 2013-02-24 23:50

@ffjia
I'm sorry, I'm fool)
Maybe it didn't work because in "post_upgrade" section group plugdev are removed and created again. Thus, user is no longer part of the group. I think that I probably looked a group previously, when user was part of the group.
I'm so sorry...)

Anonymous comment on 2013-02-24 15:40

@ffjia You have to use "strace" (pacman -S strace) to list all the system calls done by the program :
$ strace -f fingerprint-gui 2>&1 | grep "open"
(-f : "Trace child processes as they are created", 2>&1 because strace output on stderr and we want to send it to grep, grep "open" because we only want to look at the file opening attempts, not at everything else)

When selecting the "Scan/Verify" tab, you should see some "open" system calls to different files. For me, it was especially trying to open "/etc/tc.cfg", but it failed.

After doing some researchs, it appear that those files (/etc/upek.cfg and the files in /var/upek_data) are only needed for EEPROMless sensors. Maybe your sensor has an EEPROM, and so it don't need those files, and so you don't have any problem because it never look at them ?

Once again sorry for my crappy English...

ffjia commented on 2013-02-24 14:16

@all guys - sorry for the inconvenient and thanks for help.

I use BSAPI_4.3.291Lite_SDK_for_Linux because I want to support 147e:2020 sensor. I myself installed this version, works just fine without "/etc/tc.cfg".

$ uname -a
Linux southpark.co.us 3.7.9-1-ARCH #1 SMP PREEMPT Mon Feb 18 02:13:30 EET 2013 x86_64 GNU/Linux

@macman31 - How did you find this the libbsapi look for /etc/tc.cfg?

Since many users found problem to use this verison, I removed BSAPI_4.3.291Lite_SDK_for_Linux, and still use the one bundled with fingerprint-gui.

Anonymous comment on 2013-02-24 13:04

So, I also have an Upek 147e:1002.
I found the problem ("ABSOpen() failed -1086 (An internal error occurred (ptlib: tfmerr -1086).)."), doing a lot of strace.

It appear that the libbsapi compiled from BSAPI_4.3.291Lite_SDK_for_Linux.tar.gz search the Upek configuration file specifying the location of the scanned fingerprints in "/etc/tc.cfg" instead of "/etc/upek.cfg"
It don't find the file "/etc/tc.cfg", so it fallback to the default folder, "/etc/tcstore" (instead of /var/upek_data), which don't exist, causing the error.

A quick (and dirty) fix would be :
cp -p /etc/upek.cfg /etc/tc.cfg
With that fix, everything is working as it should.

A better fix would be to use the libbsapi bundled with fingerprint-gui-1.04.tar.gz, instead of getting it from BSAPI_4.3.291Lite_SDK_for_Linux.tar.gz : it use the right configuration file, /etc/upek.cfg directly.

I hope this helped ! And sorry for my English, I'm French.

arcanis commented on 2013-02-22 18:48

@ffjia
what was added in current release? Animation and what else? BSAPI or fingerprint-gui.patch& Or both? Because sudo doesn't always work in graphical interface (KDE/awesome) %)

arcanis commented on 2013-02-22 18:44

@ffjia
what was added in current release? Animation and what else? BSAPI or fingerprint-gui.patch& Or both? Because sudo doesn't always work in graphical interface (KDE/awesome) %)

jacook commented on 2013-02-22 17:12

Yes -- for some reason, ever since upgrading a few days ago. I am having the exact same problem with the same error message. I also have the Upek 147e:1002

ffjia commented on 2013-02-22 00:11

@arcanis - I updated to this version myself, everything is fine to me. Your sensor id is different though.

$ lsusb | grep Upek
Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor

It maybe caused by the BSAPI SDK.

Anyone else encounter this problem?

arcanis commented on 2013-02-20 23:27

I deleted fingerprint-gui.patch, finger-swipe-animation.tar and BSAPI and all work

arcanis commented on 2013-02-20 17:03

After upgrading doesn't work using sudo/su (login in tty to)
For user and for root: "Access denied" (both in plugdev-group).
# lsusb | grep Upek
Bus 001 Device 004: ID 147e:1002 Upek
# ls -l /dev/bus/usb/001/004
crw-rw-r-- 1 root plugdev 189, 3 фев 20 20:50 /dev/bus/usb/001/004
# journalctl -b | grep fingerprint-gui
...
фев 20 20:50:35 ARCANIS fingerprint-gui[976]: ABSOpen() failed -1086 (An internal error occurred (ptlib: tfmerr -1086).).
...

arcanis commented on 2013-02-20 17:01

After upgrading doesn't work(
For user and for root: "Access denied" (both in plugdev-group).
# lsusb | grep Upek
Bus 001 Device 004: ID 147e:1002 Upek
# ls -l /dev/bus/usb/001/004
crw-rw-r-- 1 root plugdev 189, 3 фев 20 20:50 /dev/bus/usb/001/004
# journalctl -b | grep fingerprint-gui
...
фев 20 20:50:35 ARCANIS fingerprint-gui[976]: ABSOpen() failed -1086 (An internal error occurred (ptlib: tfmerr -1086).).
...

arcanis commented on 2013-02-20 16:57

After upgrading doesn't work(
For user and for root: "Access denied" (both in plugdev-group).
# lsusb | grep Upek
Bus 001 Device 004: ID 147e:1002 Upek
# ls -l /dev/bus/usb/001/004
crw-rw-r-- 1 root plugdev 189, 3 фев 20 20:50 /dev/bus/usb/001/004
# journalctl -b | grep fingerprint-gui
...
фев 20 20:50:35 ARCANIS fingerprint-gui[976]: ABSOpen() failed -1086 (An internal error occurred (ptlib: tfmerr -1086).).
...

ffjia commented on 2013-02-20 14:04

Updates:

* Thanks to NCyril Andreatta, now this package support UPEK 147e:2020 sensor (Lenovo W5{2,3}0, T430s).
* Use new animated image created by Anton Krug [0]

[0] http://www.antonkrug.eu/articles/2012/10/26/mine-animation-for-fingerprintgui

If you are not interested in those updates, you do not have to update to this version.

ffjia commented on 2013-02-16 08:43

@flockyrocky

I do not use Gnome, so I do not know excatly what the cause of your issue. Maybe you should contact with the upstream, with more detail info.

flockyrocky commented on 2013-02-15 14:53

@ffjia
the same issue here. I even reinstalled the whole system but still got the same issue.

ffjia commented on 2012-11-21 00:17

@alphazo - I use KDE, so I cannot re-produce your issue. And I'm not sure why this package could break your login process, even with pure console? Does that mean you mistakenly modified pam files?

alphazo commented on 2012-11-20 13:22

This package breaks Gnome 3.6. Impossible to start gnome-shell (Oops window) when using any DM (GDM, KDM.. or pure console). Happened on my existing platform, fresh install and also inside VM.

ffjia commented on 2012-10-30 13:41

@haagch - I'm sorry, could you please tell me what will happen if do not add "-j1" switch?

haagch commented on 2012-10-26 17:05

Please make with 1 job in package(), it has a good chance of failing otherwise by accessing files that are not yet in their correct place:

make -j1 INSTALL_ROOT=${pkgdir}/ install || return 1

teateawhy commented on 2012-05-06 15:37

temporary workaround for the PAM update in core:

mv /lib/security/pam_fingerprint-gui.so /usr/lib/security

ffjia commented on 2012-05-06 09:25

@chneukirchen, thanks for reminding.

Adding "LIB=/usr/lib" to "qmake" seems solve the problem. After new pam hit [core], I'll update this package.

chneukirchen commented on 2012-05-05 15:39

With the new pam 1.1.5-3, pam modules need to go to /usr/lib/security.

ffjia commented on 2012-04-22 02:45

Thanks a-st, package updated.

a-st commented on 2012-04-21 18:08

Thanks for the PKGBUILD but the package needs some patching because of GCC

Patch is available here http://dpaste.com/735163/

Anonymous comment on 2012-03-12 00:29

Please update to 1.04. Thanks in advance!

ffjia commented on 2012-01-30 01:54

Updated.

Anonymous comment on 2012-01-26 02:21

Thanks. Please update to 1.03.

ffjia commented on 2011-11-15 09:06

Update to 1.02.

vdemin commented on 2011-11-15 08:50

Thanks. Are you planning to update the package version to 1.02?

ffjia commented on 2011-11-15 06:20

@zersaa, thanks & update.

ffjia commented on 2011-11-15 06:19

@zersaa, thanks & update.

vdemin commented on 2011-11-10 16:42

libfprint 0.4.0-1 in extra, time to change depends?

ffjia commented on 2011-02-07 12:55

Add LIBPOLKIT_QT argument, bump to pkgrel 2. Please update.

Anonymous comment on 2011-02-02 02:04

fails to compile for me as well

Anonymous comment on 2011-02-01 07:10

Apparantly latest polkit-qt (polkit-qt-0.99.0-1) will cause the package build to fail.

Up to version polkit-qt-0.96.1-3 everything works ok.

Anonymous comment on 2010-12-14 00:50

Swiftgeek thanks for the clue "sudo -u username sudo -i"
Now sudo no longer produces the error:

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

A hint if you haven't already thought about it:
In order to avoid writing each time "sudo -u username sudo...." just add the following line to your .bashrc:
alias sudo='sudo -u username sudo'

Chears! :P

ffjia commented on 2010-12-13 01:16

http://aur.pastebin.com/sJgSHG7k

swiftgeek commented on 2010-12-12 12:06

version before october

ffjia commented on 2010-12-12 10:30

@swiftgeek, what do you mean the "older pkgbuilds"?

Please if you thought it's a bug, file a bug report in fingerprint-gui bbs.

swiftgeek commented on 2010-12-11 21:43

ffija: have u older pkgbuilds etc?

swiftgeek commented on 2010-12-11 21:21

su -c "dbus-launch --exit-with-session /usr/lib/fingerprint-gui/fingerprint-plugin" from user gnome-session, output:

Qt: Session management error: None of the authentication protocols specified are supported
81788933

it should works without dbus-lanuch --exit-with-session so this is probably fingerprint-gui bug, not arch's

swiftgeek commented on 2010-12-11 21:20

su -c "dbus-launch --exit-with-session /usr/lib/fingerprint-gui/fingerprint-plugin" from user gnome-session, output:

Qt: Session management error: None of the authentication protocols specified are supported
81788933

swiftgeek commented on 2010-12-11 21:00

This is fancy one ;D
If i run it from root's gnome session by "sudo -u swiftgeek sudo -i" it works!

swiftgeek commented on 2010-12-11 20:39

gnome-session& launched from xterm(.xinitrc) => in xterm fingerprint prompt works, but from any terminal launched from gnome-session not...
gnome-session launched from fluxbox(.xinitrc) => fingerprint prompt works in gnome-session!

ffjia commented on 2010-12-03 01:06

Thanks xpolar, I add "polkit-qt" to makedepends array.

Anonymous comment on 2010-12-02 19:38

It seems you need to add polkit-qt to dependencies.

ffjia commented on 2010-12-02 01:33

No, someone encountered difficulties in compiling kernel with make from
testing repo. I thought that maybe the cause of this issue.

Since you do not enable testing repo, I have no idea about the error....

swiftgeek commented on 2010-12-01 19:24

whole testing repo? it's really bad idea...

ffjia commented on 2010-12-01 12:35

@swiftgeek

I compiled the package again, everything was fine.

Did you enable testing repo?

swiftgeek commented on 2010-12-01 09:52

g++ -m64 -Wl,--hash-style=gnu -Wl,--as-needed -Wl,-O1 -o fingerprint-helper DeviceHandler.o PermissionHandler.o UsbDevice.o UpekDevice.o GenericDevice.o FingerprintData.o FingerprintDiscoverer.o xmlwriter.o UserSettings.o PamGUI.o PamNonGUI.o FingerprintHelper.o moc_DeviceHandler.o moc_FingerprintDevice.o moc_FingerprintData.o moc_FingerprintDiscoverer.o moc_PamGUI.o moc_PamNonGUI.o qrc_widget-res.o -L/usr/lib -lusb-1.0 -lfprint -lfakekey -lX11 -ldl -L/usr/lib -lqca -lpthread -lQtXml -lQtGui -lQtCore
make[2]: Leaving directory `/tmp/yaourt-tmp-swiftgeek/aur-fingerprint-gui/src/fingerprint-gui-1.00-rc3/bin/fingerprint-gui'
make[2]: Leaving directory `/tmp/yaourt-tmp-swiftgeek/aur-fingerprint-gui/src/fingerprint-gui-1.00-rc3/bin/fingerprint-helper'
make[1]: Leaving directory `/tmp/yaourt-tmp-swiftgeek/aur-fingerprint-gui/src/fingerprint-gui-1.00-rc3/bin'
make: *** [sub-bin-make_default] Error 2

ffjia commented on 2010-12-01 05:37

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

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?


Anonymous comment on 2010-11-19 10:44

@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

@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

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

@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

Anonymous comment on 2010-10-09 09:05

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

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 :)

Anonymous comment on 2010-09-09 17:15

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.

:)

Anonymous comment on 2010-09-09 16:22

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?

ffjia commented on 2010-09-09 08:52

Ok, I should read the Install-step-by-step doc carefully. Change the
"auth required pam_unix.so" line to:

"auth sufficient pam_unix.so nullok try_first_pass"

make it works...

ffjia commented on 2010-09-09 08:10

Cool, dose your laptop use UPEK fingerprint readers?

What about your PAM settings? Did you make su work both keyboard and
fingerprint reader?

My pam.d/su:

#%PAM-1.0
auth sufficient pam_rootok.so
# Uncomment the following line to implicitly trust users in the "wheel" group.
#auth sufficient pam_wheel.so trust use_uid
# Uncomment the following line to require a user to be in the "wheel" group.
#auth required pam_wheel.so use_uid
auth sufficient pam_fingerprint-gui.so debug
auth required pam_unix.so
account required pam_unix.so
session required pam_unix.so

I have to Press enter key before typing password...

Anonymous comment on 2010-09-08 19:44

Works perfectly on CLevo M860TU in both Arch i686 and x86_64

Thanks for this great package and great work

ffjia commented on 2010-09-03 01:37

Improved PKGBUILD and fingerprint-gui.install files, special thanks to David.

ffjia commented on 2010-09-03 01:36

Improved PKGBUILD and fingerprint-gui.install files, special thanks to Daivd.

ffjia commented on 2010-09-02 01:08

New version released.

ffjia commented on 2010-08-20 06:14

Initial upload

Successfully tested on Upek Fingerprint Sensor of Thinkpad T410s in Arch x86_64.

The binaries are installed to "/usr/local/bin/", cause it's hardcoded in Globals.h