Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: Issue with fprintd 1.94.2-2 and PAM (Read 426 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

Issue with fprintd 1.94.2-2 and PAM

I allow sudo w/ fingerprint on one of my machines, however since updating fprintd last week I'm always immediately prompted for a password instead. Is anyone else having this problem or maybe have any idea if something changed?

Code: [Select]
# lsusb | grep Fingerprint
Bus 005 Device 006: ID 06cb:00bd Synaptics, Inc. Prometheus MIS Touch Fingerprint Reader
  idProduct          0x00bd Prometheus MIS Touch Fingerprint Reader

Code: [Select]
# cat /etc/pam.d/sudo
#%PAM-1.0
auth	sufficient	pam_fprintd.so
auth	include	system-auth
account	include	system-auth
session	include	system-auth

fprintd-verify also still works as expected, but here's the output from "sudo env G_MESSAGES_DEBUG=all /usr/lib/fprintd -t" anyway

Code: [Select]
(fprintd:10867): GLib-GIO-DEBUG: 22:12:50.902: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
(fprintd:10867): fprintd-DEBUG: 22:12:50.903: About to load configuration file '/etc/fprintd.conf'
(fprintd:10867): fprintd-DEBUG: 22:12:50.903: Launching FprintObject
(fprintd:10867): libfprint-context-DEBUG: 22:12:50.903: Initializing FpContext (libfprint version 1.94.4)
(fprintd:10867): fprintd-DEBUG: 22:12:50.910: Preparing devices for resume
(fprintd:10867): libfprint-context-DEBUG: 22:12:50.910: No driver found for USB device 1D6B:0003
(fprintd:10867): libfprint-context-DEBUG: 22:12:50.910: No driver found for USB device 8087:0032
(fprintd:10867): libfprint-context-DEBUG: 22:12:50.910: No driver found for USB device 1D6B:0002
(fprintd:10867): libfprint-context-DEBUG: 22:12:50.910: No driver found for USB device 1D6B:0003
(fprintd:10867): libfprint-context-DEBUG: 22:12:50.910: No driver found for USB device 1D6B:0002
(fprintd:10867): libfprint-context-DEBUG: 22:12:50.910: No driver found for USB device 1D6B:0003
(fprintd:10867): libfprint-context-DEBUG: 22:12:50.910: No driver found for USB device 5986:910C
(fprintd:10867): libfprint-context-DEBUG: 22:12:50.910: No driver found for USB device 1D6B:0002
(fprintd:10867): libfprint-synaptics-DEBUG: 22:12:50.910: 10407187218: ../libfprint/libfprint/drivers/synaptics/synaptics.c:1231
(fprintd:10867): fprintd-DEBUG: 22:12:51.020: Got delay inhibitor for sleep.
(fprintd:10867): libfprint-synaptics-DEBUG: 22:12:51.021: Build Time: 1629962591
(fprintd:10867): libfprint-synaptics-DEBUG: 22:12:51.021: Build Num: 3478575
(fprintd:10867): libfprint-synaptics-DEBUG: 22:12:51.021: Version: 10.1
(fprintd:10867): libfprint-synaptics-DEBUG: 22:12:51.021: Target: 1
(fprintd:10867): libfprint-synaptics-DEBUG: 22:12:51.021: Product: 65
(fprintd:10867): libfprint-synaptics-DEBUG: 22:12:51.021: sequence number is 1
(fprintd:10867): libfprint-SSM-DEBUG: 22:12:51.021: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:10867): libfprint-SSM-DEBUG: 22:12:51.021: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:10867): libfprint-device-DEBUG: 22:12:51.038: Device reported probe completion
(fprintd:10867): libfprint-SSM-DEBUG: 22:12:51.039: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:10867): libfprint-device-DEBUG: 22:12:51.039: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(fprintd:10867): libfprint-device-DEBUG: 22:12:51.039: Not updating temperature model, device can run continuously!
(fprintd:10867): fprintd-DEBUG: 22:12:51.041: Device Synaptics Sensors scan type changed to 'press'
(fprintd:10867): fprintd-DEBUG: 22:12:51.041: Device Synaptics Sensors enroll stages changed to 9
(fprintd:10867): fprintd-DEBUG: 22:12:51.041: Finger present 0
(fprintd:10867): fprintd-DEBUG: 22:12:51.041: Finger needed 0
(fprintd:10867): fprintd-DEBUG: 22:12:51.041: entering main loop
(fprintd:10867): fprintd-DEBUG: 22:12:51.041: D-Bus service launched with name: net.reactivated.Fprint
(fprintd:10867): fprintd-DEBUG: 22:13:29.943: Requesting authorization from :1.124 to call method 'Claim' for device 'Synaptics Sensors'
(fprintd:10867): fprintd-DEBUG: 22:13:29.943: Getting authorization to perform Polkit action net.reactivated.fprint.device.verify
(fprintd:10867): fprintd-DEBUG: 22:13:29.946: Authorization granted to :1.124 to call method 'Claim' for device 'Synaptics Sensors'!
(fprintd:10867): fprintd-DEBUG: 22:13:29.946: user 'andy' claiming the device: 0
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.058: 10446334970: ../libfprint/libfprint/drivers/synaptics/synaptics.c:1391
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.058: sequence number is 2
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.058: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:10867): GLib-GIO-DEBUG: 22:13:30.058: GTask [gio] D-Bus interface method dispatch (source object: 0x5581474bfb10, source tag: 0x7f195cacef50) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.058: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:10867): libfprint-device-DEBUG: 22:13:30.058: Device reported open completion
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.059: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:10867): libfprint-device-DEBUG: 22:13:30.059: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(fprintd:10867): libfprint-device-DEBUG: 22:13:30.059: Not updating temperature model, device can run continuously!
(fprintd:10867): fprintd-DEBUG: 22:13:30.059: claimed device 0
(fprintd:10867): fprintd-DEBUG: 22:13:30.060: Requesting authorization from :1.124 to call method 'ListEnrolledFingers' for device 'Synaptics Sensors'
(fprintd:10867): fprintd-DEBUG: 22:13:30.060: Getting authorization to perform Polkit action net.reactivated.fprint.device.verify
(fprintd:10867): fprintd-DEBUG: 22:13:30.063: Authorization granted to :1.124 to call method 'ListEnrolledFingers' for device 'Synaptics Sensors'!
(fprintd:10867): fprintd-DEBUG: 22:13:30.063: file_storage_discover_prints() for user 'andy' in '/var/lib/fprint/andy/synaptics/5409c38cc3a2'
(fprintd:10867): fprintd-DEBUG: 22:13:30.071: file_storage_print_data_load(): loaded '/var/lib/fprint/andy/synaptics/5409c38cc3a2/7' Success
(fprintd:10867): GLib-GIO-DEBUG: 22:13:30.071: GTask [gio] D-Bus interface method dispatch (source object: 0x5581474bfb10, source tag: 0x7f195cacef50) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:10867): fprintd-DEBUG: 22:13:30.071: Requesting authorization from :1.124 to call method 'VerifyStart' for device 'Synaptics Sensors'
(fprintd:10867): fprintd-DEBUG: 22:13:30.071: Getting authorization to perform Polkit action net.reactivated.fprint.device.verify
(fprintd:10867): fprintd-DEBUG: 22:13:30.074: Authorization granted to :1.124 to call method 'VerifyStart' for device 'Synaptics Sensors'!
(fprintd:10867): fprintd-DEBUG: 22:13:30.074: file_storage_print_data_load(): loaded '/var/lib/fprint/andy/synaptics/5409c38cc3a2/7' Success
(fprintd:10867): fprintd-DEBUG: 22:13:30.074: start verification device 0 finger right-index-finger
(fprintd:10867): libfprint-device-DEBUG: 22:13:30.074: Not updating temperature model, device can run continuously!
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.074: data is 0x5581474be6e0
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.074: 10446350866: ../libfprint/libfprint/drivers/synaptics/synaptics.c:636
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.074: sequence number is 3
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.074: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:10867): GLib-GIO-DEBUG: 22:13:30.074: GTask [gio] D-Bus interface method dispatch (source object: 0x5581474bfb10, source tag: 0x7f195cacef50) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.074: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:10867): libfprint-device-DEBUG: 22:13:30.124: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(fprintd:10867): fprintd-DEBUG: 22:13:30.124: Finger present 0
(fprintd:10867): fprintd-DEBUG: 22:13:30.124: Finger needed 1
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.124: Place Finger on the Sensor!
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.124: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.127: interrupt transfer done
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.127: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.127: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.127: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.127: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:10867): libfprint-device-DEBUG: 22:13:30.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(fprintd:10867): fprintd-DEBUG: 22:13:30.127: Finger present 1
(fprintd:10867): fprintd-DEBUG: 22:13:30.127: Finger needed 1
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.127: Finger is now on the sensor
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.127: Received message with 0 sequence number 0x91, ignoring!
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.127: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.130: interrupt transfer done
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.131: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.131: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.131: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.131: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:10867): libfprint-device-DEBUG: 22:13:30.131: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(fprintd:10867): fprintd-DEBUG: 22:13:30.131: Finger present 0
(fprintd:10867): fprintd-DEBUG: 22:13:30.131: Finger needed 1
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.131: Finger is now off the sensor
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.131: Received message with 0 sequence number 0x91, ignoring!
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.131: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.134: interrupt transfer done
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.134: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.135: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.135: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.135: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.135: Finger is now off the sensor
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:30.135: Received message with 0 sequence number 0x91, ignoring!
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:30.135: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:32.038: interrupt transfer done
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.038: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.038: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.038: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.038: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:10867): libfprint-device-DEBUG: 22:13:32.038: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(fprintd:10867): fprintd-DEBUG: 22:13:32.039: Finger present 1
(fprintd:10867): fprintd-DEBUG: 22:13:32.039: Finger needed 1
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:32.039: Finger is now on the sensor
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:32.039: Received message with 0 sequence number 0x91, ignoring!
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.039: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:32.106: interrupt transfer done
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.106: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.106: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.106: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.106: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:32.106: Fingerprint image capture complete!
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.106: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:32.277: interrupt transfer done
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.278: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.278: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.278: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.278: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:32.278: Verify was successful! for user: FP1-20230124-7-A2F8623D-andy finger: 1 score: 78.960000
(fprintd:10867): libfprint-device-DEBUG: 22:13:32.278: Device reported verify result
(fprintd:10867): fprintd-DEBUG: 22:13:32.278: report_verify_status: result verify-match
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:32.278: delaying verify report until after finger removal!
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.278: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(fprintd:10867): fprintd-DEBUG: 22:13:32.279: Requesting authorization from :1.124 to call method 'VerifyStop' for device 'Synaptics Sensors'
(fprintd:10867): fprintd-DEBUG: 22:13:32.279: Authorization granted to :1.124 to call method 'VerifyStop' for device 'Synaptics Sensors'!
(fprintd:10867): GLib-GIO-DEBUG: 22:13:32.279: GTask [gio] D-Bus interface method dispatch (source object: 0x5581474bfb10, source tag: 0x7f195cacef50) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:32.729: interrupt transfer done
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.729: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.730: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.730: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.730: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:10867): libfprint-device-DEBUG: 22:13:32.730: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(fprintd:10867): fprintd-DEBUG: 22:13:32.730: Finger present 0
(fprintd:10867): fprintd-DEBUG: 22:13:32.730: Finger needed 1
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.730: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:10867): libfprint-device-DEBUG: 22:13:32.730: Device reported verify completion
(fprintd:10867): libfprint-device-DEBUG: 22:13:32.730: Device reported finger status change: FP_FINGER_STATUS_NONE
(fprintd:10867): fprintd-DEBUG: 22:13:32.730: Finger present 0
(fprintd:10867): fprintd-DEBUG: 22:13:32.730: Finger needed 0
(fprintd:10867): libfprint-device-DEBUG: 22:13:32.730: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
(fprintd:10867): libfprint-device-DEBUG: 22:13:32.730: Not updating temperature model, device can run continuously!
(fprintd:10867): fprintd-DEBUG: 22:13:32.730: verify_cb: result verify-match
(fprintd:10867): fprintd-DEBUG: 22:13:32.732: Requesting authorization from :1.124 to call method 'Release' for device 'Synaptics Sensors'
(fprintd:10867): fprintd-DEBUG: 22:13:32.732: Authorization granted to :1.124 to call method 'Release' for device 'Synaptics Sensors'!
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:32.732: 10449009016: ../libfprint/libfprint/drivers/synaptics/synaptics.c:1412
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:32.732: sequence number is 4
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.732: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:10867): GLib-GIO-DEBUG: 22:13:32.732: GTask [gio] D-Bus interface method dispatch (source object: 0x5581474bfb10, source tag: 0x7f195cacef50) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.732: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:10867): libfprint-synaptics-DEBUG: 22:13:32.732: Fingerprint sensor ready to be powered down
(fprintd:10867): libfprint-device-DEBUG: 22:13:32.732: Device reported close completion
(fprintd:10867): libfprint-SSM-DEBUG: 22:13:32.733: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:10867): libfprint-device-DEBUG: 22:13:32.733: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(fprintd:10867): libfprint-device-DEBUG: 22:13:32.733: Not updating temperature model, device can run continuously!
(fprintd:10867): fprintd-DEBUG: 22:13:32.733: released device 0

Re: Issue with fprintd 1.94.2-2 and PAM

Reply #1 –
Yes actually. I had to disable pam support for it to build otherwise it kept looking for libsystemd. I'm actually not totally sure how it built in the past (maybe some libsystemd pc hacks). I think master currently supports libelogind so I think next version I should be able to turn it back on.

Re: Issue with fprintd 1.94.2-2 and PAM

Reply #2 –
Understood, thanks for the clarification

Re: Issue with fprintd 1.94.2-2 and PAM

Reply #3 –
Actually nevermind, I was able to cherrypick the commit in question so it should work again.

Re: Issue with fprintd 1.94.2-2 and PAM

Reply #4 –
Just upgraded and so far so good. Thanks again!