This worked for me, if I ran but if I ran just It would not work.
I tried the workaround of adding my user to the plugdev group and the I got
This turned out to be because the /home/user/.fprints directory was owned by root, so I did
error loading enrolled prints
it started working.
sudo chown -R $USER /home/user/.fprints
Is this correct, or have I opened a security hole?
Although fprint_demo works on my Tecra A9, it does report a couple of errors while scanning or verifying
Both messages are produced for each action.
upekts:error [read_msg] non-zero bytes in cmd response
upekts:error [read_msg28] expected response, got -1 seq=0
I get this every time the scanner is used, eg verifying your finger and enrolling your finger produce this error, but deleting a fingerprint file does not. Also on enrolling, I only get the error once, not three times.