Arch Linux

Lockheed

Member

Registered: 2010-03-16

Posts: 1,550

[solved] Fingerprint password input too verbose

I finally got my fingerprint authentication working. The problem is, that it produces a lot of useless verbose output in both console, and no xscreensaver (whenever it asks for password).

Here is how it was before setting it up:

$ geany
[sudo] password for john-smith: 

And here is how it is now:

$ geany
aes2550:debug [finger_det_data_cb] transfer completed, len: 0002, data: 83 04
aes2550:debug [start_finger_detection] 
aes2550:debug [finger_det_data_cb] transfer completed, len: 0002, data: 83 04
aes2550:debug [start_finger_detection] 
aes2550:debug [finger_det_data_cb] transfer completed, len: 0002, data: 83 04
aes2550:debug [start_finger_detection] 
aes2550:debug [finger_det_data_cb] transfer completed, len: 0002, data: 83 04
aes2550:debug [start_finger_detection] 
aes2550:debug [finger_det_data_cb] transfer completed, len: 0002, data: 83 04
aes2550:debug [start_finger_detection] 
aes2550:debug [finger_det_data_cb] transfer completed, len: 0002, data: 83 04
aes2550:debug [start_finger_detection] 
aes2550:debug [finger_det_data_cb] transfer completed, len: 0002, data: 83 04
aes2550:debug [start_finger_detection] 
aes2550:debug [finger_det_data_cb] transfer completed, len: 0002, data: 83 04
aes2550:debug [start_finger_detection] 
aes2550:debug [finger_det_data_cb] transfer completed, len: 0002, data: 83 04
aes2550:debug [start_finger_detection] 


<repeates the above two lines for several seconds>

aes2550:debug [finger_det_data_cb] transfer completed, len: 0002, data: 83 84
fp:debug [fpi_imgdev_report_finger_status] finger on sensor
aes2550:debug [start_capture] 
drv:debug [__ssm_call_handler] 0x7fa830002b80 entering state 0
drv:debug [__ssm_call_handler] 0x7fa830002b80 entering state 1
aes2550:debug [capture_read_data_cb] request completed, len: 0321
aes2550:debug [capture_read_data_cb] data: e0 03
drv:debug [__ssm_call_handler] 0x7fa830002b80 entering state 1
aes2550:debug [capture_read_data_cb] request completed, len: 0321
aes2550:debug [capture_read_data_cb] data: e0 03
drv:debug [__ssm_call_handler] 0x7fa830002b80 entering state 1
aes2550:debug [capture_read_data_cb] request completed, len: 0321
aes2550:debug [capture_read_data_cb] data: e0 03

<repeates the above two lines for several seconds>


aes2550:debug [capture_read_data_cb] data: db 00
aes2550:debug [capture_read_data_cb] Got 3 heartbeats => finger removed
drv:debug [__ssm_call_handler] 0x7fa830002b80 entering state 2
fp:debug [fpi_img_new] length=193536
aeslib:debug [aes_assemble] reversed scan direction
fp:debug [fpi_imgdev_image_captured] 
fp:debug [fpi_img_detect_minutiae] minutiae scan completed in 0.048256 secs
fp:debug [fpi_img_detect_minutiae] detected 55 minutiae
fp:debug [print_data_new] length=2404 driver=0c devtype=0000
fp:debug [fpi_imgdev_report_finger_status] finger removed
async:debug [fpi_drvcb_report_identify_result] result 1
drv:debug [fpi_ssm_mark_completed] 0x7fa830002b80 completed with status 0
aes2550:debug [capture_sm_complete] Capture completed
aes2550:debug [start_finger_detection] 
sync:debug [fp_identify_finger_img] result: match at offset 6
async:debug [fp_async_identify_stop] 
aes2550:debug [finger_det_data_cb] transfer completed, len: 0321, data: e0 03
aes2550:debug [start_finger_detection] 
aes2550:debug [complete_deactivation] 
fp:debug [fpi_imgdev_deactivate_complete] 
async:debug [fpi_drvcb_identify_stopped] 
sync:debug [identify_stop_cb] 
sync:debug [fp_dev_close] 
async:debug [fpi_drvcb_close_complete] 
sync:debug [sync_close_cb] 
fp:debug [fp_exit]
[sudo] password for john-smith: 

Is there some way to clean it up and disable displaying all this information? I would like to see nothing more than just one line info "scan your finger" or something similar.

Last edited by Lockheed (2013-11-28 22:01:58)

progandy

Member

Registered: 2012-05-17

Posts: 5,320

Re: [solved] Fingerprint password input too verbose

Edit: Am I correct to assume you are using libfprint to access the fingerprint scanner?
You should reduce the log level for libfprint. Don't set LIBFPRINT_DEBUG to 3, use LIBFPRINT_DEBUG=2 or less in your environment. If it does not work, you'll have to recompile libfprint without verbose logging. I believe that the arch package is compiled correctly, though

/** \ingroup core
* Set message verbosity.
*  - Level 0: no messages ever printed by the library (default)
*  - Level 1: error messages are printed to stderr
*  - Level 2: warning and error messages are printed to stderr
*  - Level 3: informational messages are printed to stdout, warning and error
*    messages are printed to stderr
*
* The default level is 0, which means no messages are ever printed. If you
* choose to increase the message verbosity level, ensure that your
* application does not close the stdout/stderr file descriptors.
*
* You are advised to set level 3. libfprint is conservative with its message
* logging and most of the time, will only log messages that explain error
* conditions and other oddities. This will help you debug your software.
*
* If the LIBFPRINT_DEBUG environment variable was set when libfprint was
* initialized, this function does nothing: the message verbosity is fixed
* to the value in the environment variable.
*
* If libfprint was compiled without any message logging, this function does
* nothing: you'll never get any messages.
*
* If libfprint was compiled with verbose debug message logging, this function
* does nothing: you'll always get messages from all levels.
*
* \param ctx the context to operate on, or NULL for the default context
* \param level debug level to set
*/

Last edited by progandy (2013-11-28 20:17:19)

---

| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |

Lockheed

Member

Registered: 2010-03-16

Posts: 1,550

Re: [solved] Fingerprint password input too verbose

Well, I am using fingerprintreader-gui with libfprint-git (but not the one from repo, because it doesn't support my reader).

Where can I set this variable? I found no .conf file in /etc/

progandy

Member

Registered: 2012-05-17

Posts: 5,320

Re: [solved] Fingerprint password input too verbose

Put it in your .bash_profile or any other profile file for your shell. Other places would be /etc/profile.d, /etc/environment, or ~/.pam_environment

---

| alias CUTF='LANG=en_XX.UTF-8@POSIX ' | alias ENGLISH='LANG=C.UTF-8 ' |

Lockheed

Member

Registered: 2010-03-16

Posts: 1,550

Re: [solved] Fingerprint password input too verbose

I did that, and confirmed it by calling "env" after reboot. However, the problem still persisted.

So I went ahead and installed official libfprint form the repos. Previously, I was using a fork because official lib did not support my reader.
In any case, it is now working fine and no more verbose messages. Thanks for your help!

Last edited by Lockheed (2013-11-28 22:01:36)