fprintd issueshttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues2023-11-24T12:18:02Zhttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues/164fprintd-verify: cycle through all fingers on swipe devices2023-11-24T12:18:02Zsu-sdfprintd-verify: cycle through all fingers on swipe devicesCan you please add an option for fprind-verify to cycle through all fingers on swipe devices?
This is important, if one finger does not work or is temporarily/permanent not available anymore. This could potentially lock some users out ot...Can you please add an option for fprind-verify to cycle through all fingers on swipe devices?
This is important, if one finger does not work or is temporarily/permanent not available anymore. This could potentially lock some users out otherwise.
pam handles this correct, it scans a finger does not care which one it is.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/163Add support for EgisTec 1c7a:05752023-11-17T10:02:45ZDominik MucAdd support for EgisTec 1c7a:0575On acer swift 3. There is support for model 0570, possibly fork code? I'll try to have look at it myself.On acer swift 3. There is support for model 0570, possibly fork code? I'll try to have look at it myself.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/158Fprintd seems tio enroll a fingerprint correctly but fails to verify or use it2023-07-09T08:43:22ZAaron BlaskoFprintd seems tio enroll a fingerprint correctly but fails to verify or use itJust to be clear, fingerprint unlocks were working perfectly until now (registered my fingerprints last august), until I tried to delete them (fprintd-delete alba4k, I wanted to try to get a better scan to avoid the sensor sometimes not ...Just to be clear, fingerprint unlocks were working perfectly until now (registered my fingerprints last august), until I tried to delete them (fprintd-delete alba4k, I wanted to try to get a better scan to avoid the sensor sometimes not recognizing my finger properly).
Now, I can apparently enroll a fingerprint correctly:
`fprintd-enroll -f right-index-finger alba4k`
```
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-completed
`
(Interestingly, while registering to get an output to post here, I got a couple of `Enroll result: enroll-disconnected` which disappeared after using `fprintd-detele` but this shouldn't be relevant)
Now, I can see my fingerprint `fprintd-list alba4k`
```
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
Fingerprints for user alba4k on Goodix MOC Fingerprint Sensor (press):
- #0: right-index-finger
```
However, `fprintd-verify alba4k` or trying to use the fingerprint anywhere will fail:
```
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
- #0: right-index-finger
Verify started!
Verifying: right-index-finger
Verify result: verify-no-match (done)
`
...and now my fingerprint is gone in ```fprintd-list alba4k```
```
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
User alba4k has no fingers enrolled for Goodix MOC Fingerprint Sensor.
```
Here are some maybe useful outputs
`lshw`
```
*-usb:0 UNCLAIMED
description: Generic USB device
product: Goodix USB2.0 MISC
vendor: Goodix Technology Co., Ltd.
physical id: 9
bus info: usb@3:9
version: 1.00
serial: UIDCF7D92AB_XXXX_MOC_B0
capabilities: usb-2.00
configuration: maxpower=100mA speed=12Mbit/s
```
`systemctl status fprintd`
```
● fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
Active: active (running) since Tue 2023-04-18 21:49:31 CEST; 30s ago
Docs: man:fprintd(1)
Main PID: 120752 (fprintd)
Tasks: 7 (limit: 18689)
Memory: 3.8M
CPU: 193ms
CGroup: /system.slice/fprintd.service
└─120752 /usr/lib/fprintd
apr 18 21:49:31 dell-xps systemd[1]: Starting Fingerprint Authentication Daemon...
apr 18 21:49:31 dell-xps fprintd[120752]: libusb: error [udev_hotplug_event] ignoring udev action change
apr 18 21:49:31 dell-xps fprintd[120752]: libusb: error [udev_hotplug_event] ignoring udev action change
apr 18 21:49:31 dell-xps systemd[1]: Started Fingerprint Authentication Daemon.
apr 18 21:49:41 dell-xps fprintd[120752]: libusb: error [udev_hotplug_event] ignoring udev action change
apr 18 21:49:41 dell-xps fprintd[120752]: libusb: error [udev_hotplug_event] ignoring udev action change
apr 18 21:49:59 dell-xps fprintd[120752]: libusb: error [udev_hotplug_event] ignoring udev action change
apr 18 21:49:59 dell-xps fprintd[120752]: libusb: error [udev_hotplug_event] ignoring udev action change
apr 18 21:49:59 dell-xps fprintd[120752]: Deleted stored finger 7 for user alba4k as it is unknown to device.
```
Also, I found [this](https://www.reddit.com/r/pop_os/comments/woi1w5/xps_13_plus_9320_fingerprint) post on reddit of someone having my same issue, but the suggested workaround doesn't seem to work for me. I do think I had it working at a certain moment, though, some days ago while trying on my won. However, the fingerpritns do not appear to get deleted if I add more than one (or at least, now always).
Some random info:
* fprintd version: 1.94.2 (tried libfprint 1.94.2 to 1.94.4 with no success, same issue using fprintd-libfprint2 from the AUR)
* Using linux-zen 6.2.11
* The sensors appears as `27c6:63bc Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC` in `lsusb`, I'm using an XPS 9320
Does anybody have any idea or has had a similar issue (many on the internet but with no solution, apparently..)? Is there any useful info I could provide?
Thanks a lot in advance :smile:
#### This issue report is just a copy of [This](https://bbs.archlinux.org/viewtopic.php?id=285186) post on the arch forums, just adjusted to use markdown formattinghttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues/156fprintd dies after some time since laptop startup, only reboot helps2023-10-15T12:42:30ZDmitrii Vinokurovfprintd dies after some time since laptop startup, only reboot helpsHi!
I've got Lenovo ThinkPad X1 Carbon Gen 8 with Kubuntu 23.04 (6.2.0-20-generic kernel) and I am facing issues with fingerprint scanner for a long time - after some time since laptop start the scanner stops working.
I tried to look a...Hi!
I've got Lenovo ThinkPad X1 Carbon Gen 8 with Kubuntu 23.04 (6.2.0-20-generic kernel) and I am facing issues with fingerprint scanner for a long time - after some time since laptop start the scanner stops working.
I tried to look at `fprintd` status when fingerprint scanner is not working, it shows:
```
[22:18]dmitriy@Gim6626-ThinkPad-X1-Carbon-Gen-8[~]$ LANG=us systemctl status fprintd.service
○ fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/lib/systemd/system/fprintd.service; static)
Active: inactive (dead)
Docs: man:fprintd(1)
Apr 30 22:52:38 Gim6626-ThinkPad-X1-Carbon-Gen-8 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
May 02 12:31:45 Gim6626-ThinkPad-X1-Carbon-Gen-8 systemd[1]: fprintd.service: Deactivated successfully.
May 04 22:10:19 Gim6626-ThinkPad-X1-Carbon-Gen-8 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
May 04 22:10:19 Gim6626-ThinkPad-X1-Carbon-Gen-8 fprintd[438453]: Ignoring device due to initialization error: endpoint stalled or request not supported
May 04 22:10:19 Gim6626-ThinkPad-X1-Carbon-Gen-8 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
May 04 22:10:49 Gim6626-ThinkPad-X1-Carbon-Gen-8 systemd[1]: fprintd.service: Deactivated successfully.
May 04 22:13:57 Gim6626-ThinkPad-X1-Carbon-Gen-8 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
May 04 22:13:57 Gim6626-ThinkPad-X1-Carbon-Gen-8 fprintd[440227]: Ignoring device due to initialization error: endpoint stalled or request not supported
May 04 22:13:57 Gim6626-ThinkPad-X1-Carbon-Gen-8 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
May 04 22:14:27 Gim6626-ThinkPad-X1-Carbon-Gen-8 systemd[1]: fprintd.service: Deactivated successfully.
```
I tried to start - it succeeds, but does not initialize the device:
```
[22:26]dmitriy@Gim6626-ThinkPad-X1-Carbon-Gen-8[~]$ LANG=us sudo systemctl start fprintd.service
[22:33]dmitriy@Gim6626-ThinkPad-X1-Carbon-Gen-8[~]$ LANG=us sudo systemctl status fprintd.service
● fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/lib/systemd/system/fprintd.service; static)
Active: active (running) since Thu 2023-05-04 22:33:34 +04; 4s ago
Docs: man:fprintd(1)
Main PID: 446918 (fprintd)
Tasks: 6 (limit: 18600)
Memory: 2.6M
CPU: 71ms
CGroup: /system.slice/fprintd.service
└─446918 /usr/libexec/fprintd
May 04 22:33:34 Gim6626-ThinkPad-X1-Carbon-Gen-8 systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
May 04 22:33:34 Gim6626-ThinkPad-X1-Carbon-Gen-8 fprintd[446918]: Ignoring device due to initialization error: endpoint stalled or request not supported
May 04 22:33:34 Gim6626-ThinkPad-X1-Carbon-Gen-8 systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
```
But full laptop reboot helps, for some time the scanner works and then it dies again.
Could anybody help, please? I tried to google it, but seems that it is quite rare issue.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/152enroll-disconnected error when running fprind-enroll2023-03-15T13:34:49Zptrenroll-disconnected error when running fprind-enrollI have a Thinkpad x1 carbon gen9 running arch linux. When I first setup the device, fprintd was working correctly. At some point it stopped working, so I first ran fprintd-delete and then tried to enroll a new fingerprint. However I am g...I have a Thinkpad x1 carbon gen9 running arch linux. When I first setup the device, fprintd was working correctly. At some point it stopped working, so I first ran fprintd-delete and then tried to enroll a new fingerprint. However I am getting the error `enroll-disconnected`.
fprintd-list <User> output
```
fprintd-list ptr
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
User ptr has no fingers enrolled for Synaptics Sensors.
```
debug logs:
```
(fprintd:8438): fprintd-DEBUG: 12:50:42.540: Requesting authorization from :1.100 to call method 'ListEnrolledFingers' for device 'Synaptics Sensors'
(fprintd:8438): fprintd-DEBUG: 12:50:42.541: Getting authorization to perform Polkit action net.reactivated.fprint.device.verify
(fprintd:8438): fprintd-DEBUG: 12:50:42.548: Authorization granted to :1.100 to call method 'ListEnrolledFingers' for device 'Synaptics Sensors'!
(fprintd:8438): fprintd-DEBUG: 12:50:42.549: file_storage_discover_prints() for user 'ptr' in '/var/lib/fprint/ptr/synaptics/fbaadd8ad210'
(fprintd:8438): fprintd-DEBUG: 12:50:42.549: scan_dev_storedir(): opendir("/var/lib/fprint/ptr/synaptics/fbaadd8ad210") failed: Error opening directory “/var/lib/fprint/ptr/synaptics/fbaadd8ad210”: No such file or directory
(fprintd:8438): GLib-GIO-DEBUG: 12:50:42.549: GTask [gio] D-Bus interface method dispatch (source object: 0x563a920bd410, source tag: 0x7f95a4d47cd0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
```
fprintd-verify
```
Using device /net/reactivated/Fprint/Device/0
ListEnrolledFingers failed: GDBus.Error:net.reactivated.Fprint.Error.NoEnrolledPrints: Failed to discover prints
```
debug logs
```
(fprintd:8438): fprintd-DEBUG: 12:53:56.850: Requesting authorization from :1.105 to call method 'Claim' for device 'Synaptics Sensors'
(fprintd:8438): fprintd-DEBUG: 12:53:56.850: Getting authorization to perform Polkit action net.reactivated.fprint.device.verify
(fprintd:8438): fprintd-DEBUG: 12:53:56.858: Authorization granted to :1.105 to call method 'Claim' for device 'Synaptics Sensors'!
(fprintd:8438): fprintd-DEBUG: 12:53:56.858: user 'ptr' claiming the device: 0
(fprintd:8438): libfprint-synaptics-DEBUG: 12:53:57.107: 1200438240: ../libfprint/libfprint/drivers/synaptics/synaptics.c:1391
(fprintd:8438): libfprint-synaptics-DEBUG: 12:53:57.108: sequence number is 17
(fprintd:8438): libfprint-SSM-DEBUG: 12:53:57.108: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:8438): GLib-GIO-DEBUG: 12:53:57.108: GTask [gio] D-Bus interface method dispatch (source object: 0x563a920bd410, source tag: 0x7f95a4d47cd0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:8438): libfprint-SSM-DEBUG: 12:53:57.108: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:8438): libfprint-device-DEBUG: 12:53:57.108: Device reported open completion
(fprintd:8438): libfprint-SSM-DEBUG: 12:53:57.108: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:8438): libfprint-device-DEBUG: 12:53:57.108: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(fprintd:8438): libfprint-device-DEBUG: 12:53:57.108: Not updating temperature model, device can run continuously!
(fprintd:8438): fprintd-DEBUG: 12:53:57.108: claimed device 0
(fprintd:8438): fprintd-DEBUG: 12:53:57.110: Requesting authorization from :1.105 to call method 'ListEnrolledFingers' for device 'Synaptics Sensors'
(fprintd:8438): fprintd-DEBUG: 12:53:57.111: Getting authorization to perform Polkit action net.reactivated.fprint.device.verify
(fprintd:8438): fprintd-DEBUG: 12:53:57.121: Authorization granted to :1.105 to call method 'ListEnrolledFingers' for device 'Synaptics Sensors'!
(fprintd:8438): fprintd-DEBUG: 12:53:57.121: file_storage_discover_prints() for user 'ptr' in '/var/lib/fprint/ptr/synaptics/fbaadd8ad210'
(fprintd:8438): fprintd-DEBUG: 12:53:57.121: scan_dev_storedir(): opendir("/var/lib/fprint/ptr/synaptics/fbaadd8ad210") failed: Error opening directory “/var/lib/fprint/ptr/synaptics/fbaadd8ad210”: No such file or directory
(fprintd:8438): GLib-GIO-DEBUG: 12:53:57.121: GTask [gio] D-Bus interface method dispatch (source object: 0x563a920bd410, source tag: 0x7f95a4d47cd0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:8438): libfprint-synaptics-DEBUG: 12:53:57.123: 1200453464: ../libfprint/libfprint/drivers/synaptics/synaptics.c:1412
(fprintd:8438): libfprint-synaptics-DEBUG: 12:53:57.123: sequence number is 18
(fprintd:8438): libfprint-SSM-DEBUG: 12:53:57.123: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:8438): libfprint-SSM-DEBUG: 12:53:57.123: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:8438): libfprint-synaptics-DEBUG: 12:53:57.176: Fingerprint sensor ready to be powered down
(fprintd:8438): libfprint-device-DEBUG: 12:53:57.176: Device reported close completion
(fprintd:8438): libfprint-SSM-DEBUG: 12:53:57.176: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:8438): libfprint-device-DEBUG: 12:53:57.176: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(fprintd:8438): libfprint-device-DEBUG: 12:53:57.176: Not updating temperature model, device can run continuously!
```
fprintd-enroll
```
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-disconnected
```
debug logs
```
(fprintd:8438): fprintd-DEBUG: 12:52:32.260: Requesting authorization from :1.102 to call method 'Claim' for device 'Synaptics Sensors'
(fprintd:8438): fprintd-DEBUG: 12:52:32.260: Getting authorization to perform Polkit action net.reactivated.fprint.device.verify
(fprintd:8438): fprintd-DEBUG: 12:52:32.267: Authorization granted to :1.102 to call method 'Claim' for device 'Synaptics Sensors'!
(fprintd:8438): fprintd-DEBUG: 12:52:32.267: user 'ptr' claiming the device: 0
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:32.514: 1115844908: ../libfprint/libfprint/drivers/synaptics/synaptics.c:1391
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:32.514: sequence number is 14
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:32.514: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:8438): GLib-GIO-DEBUG: 12:52:32.514: GTask [gio] D-Bus interface method dispatch (source object: 0x563a920bd410, source tag: 0x7f95a4d47cd0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:32.515: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:8438): libfprint-device-DEBUG: 12:52:32.515: Device reported open completion
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:32.515: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:8438): libfprint-device-DEBUG: 12:52:32.515: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(fprintd:8438): libfprint-device-DEBUG: 12:52:32.515: Not updating temperature model, device can run continuously!
(fprintd:8438): fprintd-DEBUG: 12:52:32.515: claimed device 0
(fprintd:8438): fprintd-DEBUG: 12:52:32.517: Requesting authorization from :1.102 to call method 'EnrollStart' for device 'Synaptics Sensors'
(fprintd:8438): fprintd-DEBUG: 12:52:32.517: Getting authorization to perform Polkit action net.reactivated.fprint.device.enroll
(fprintd:8438): fprintd-DEBUG: 12:52:34.610: Authorization granted to :1.102 to call method 'EnrollStart' for device 'Synaptics Sensors'!
(fprintd:8438): fprintd-DEBUG: 12:52:34.610: file_storage_print_data_load(): loaded '/var/lib/fprint/ptr/synaptics/fbaadd8ad210/7' Unknown error -2
(fprintd:8438): fprintd-DEBUG: 12:52:34.610: start enrollment device 0 finger 7
(fprintd:8438): fprintd-DEBUG: 12:52:34.611: file_storage_discover_prints() for user 'root' in '/var/lib/fprint/root/synaptics/fbaadd8ad210'
(fprintd:8438): fprintd-DEBUG: 12:52:34.611: file_storage_print_data_load(): loaded '/var/lib/fprint/root/synaptics/fbaadd8ad210/7' Success
(fprintd:8438): fprintd-DEBUG: 12:52:34.611: file_storage_discover_prints() for user 'root' in '/var/lib/fprint/root/synaptics/fbaadd8ad210'
(fprintd:8438): fprintd-DEBUG: 12:52:34.611: file_storage_print_data_load(): loaded '/var/lib/fprint/root/synaptics/fbaadd8ad210/7' Success
(fprintd:8438): libfprint-device-DEBUG: 12:52:34.611: Not updating temperature model, device can run continuously!
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:34.611: data is 0x563a920adc90
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:34.611: 1117941683: ../libfprint/libfprint/drivers/synaptics/synaptics.c:851
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:34.611: sequence number is 15
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:34.611: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:8438): GLib-GIO-DEBUG: 12:52:34.611: GTask [gio] D-Bus interface method dispatch (source object: 0x563a920bd410, source tag: 0x7f95a4d47cd0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:34.611: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:34.619: Place Finger on the Sensor!
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:34.619: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:36.032: interrupt transfer done
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.032: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.033: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.033: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.033: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:8438): libfprint-device-DEBUG: 12:52:36.033: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(fprintd:8438): fprintd-DEBUG: 12:52:36.033: Finger present 1
(fprintd:8438): fprintd-DEBUG: 12:52:36.033: Finger needed 0
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:36.033: Finger is now on the sensor
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:36.033: Received message with 0 sequence number 0x91, ignoring!
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.033: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:36.100: interrupt transfer done
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.100: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.101: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.101: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.101: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.101: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:36.236: interrupt transfer done
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.236: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.237: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.237: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.237: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:8438): libfprint-synaptics-WARNING **: 12:52:36.237: identify has failed: 502
(fprintd:8438): libfprint-device-DEBUG: 12:52:36.237: Device reported identify completion
(fprintd:8438): libfprint-device-DEBUG: 12:52:36.237: Device reported finger status change: FP_FINGER_STATUS_NONE
(fprintd:8438): fprintd-DEBUG: 12:52:36.237: Finger present 0
(fprintd:8438): fprintd-DEBUG: 12:52:36.237: Finger needed 0
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.237: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:8438): libfprint-device-DEBUG: 12:52:36.237: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(fprintd:8438): libfprint-device-DEBUG: 12:52:36.237: Not updating temperature model, device can run continuously!
(fprintd:8438): fprintd-WARNING **: 12:52:36.237: Device reported an error during identify for enroll: Unexpected result from device 502
(fprintd:8438): fprintd-DEBUG: 12:52:36.239: Requesting authorization from :1.102 to call method 'EnrollStop' for device 'Synaptics Sensors'
(fprintd:8438): fprintd-DEBUG: 12:52:36.239: Authorization granted to :1.102 to call method 'EnrollStop' for device 'Synaptics Sensors'!
(fprintd:8438): GLib-GIO-DEBUG: 12:52:36.239: GTask [gio] D-Bus interface method dispatch (source object: 0x563a920bd410, source tag: 0x7f95a4d47cd0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:8438): fprintd-DEBUG: 12:52:36.240: Requesting authorization from :1.102 to call method 'Release' for device 'Synaptics Sensors'
(fprintd:8438): fprintd-DEBUG: 12:52:36.240: Authorization granted to :1.102 to call method 'Release' for device 'Synaptics Sensors'!
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:36.240: 1119571171: ../libfprint/libfprint/drivers/synaptics/synaptics.c:1412
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:36.240: sequence number is 16
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.240: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:8438): GLib-GIO-DEBUG: 12:52:36.241: GTask [gio] D-Bus interface method dispatch (source object: 0x563a920bd410, source tag: 0x7f95a4d47cd0) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.241: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:8438): libfprint-synaptics-DEBUG: 12:52:36.241: Fingerprint sensor ready to be powered down
(fprintd:8438): libfprint-device-DEBUG: 12:52:36.241: Device reported close completion
(fprintd:8438): libfprint-SSM-DEBUG: 12:52:36.241: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:8438): libfprint-device-DEBUG: 12:52:36.241: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(fprintd:8438): libfprint-device-DEBUG: 12:52:36.241: Not updating temperature model, device can run continuously!
(fprintd:8438): fprintd-DEBUG: 12:52:36.241: released device 0
```https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/148Coredump with FPC device2022-12-07T10:04:16Zjim zhangCoredump with FPC deviceEnviroment:
Ubuntu 20.04
fprintd: the latest version 1.94.2. The commit id:eeaacececf6ebbc3437594ee883bfc459a735a4e
libfprint: the latest version from source code 1.94.5. Commit id: 89509c76f4a533217088607e1f0822510fe97859
...Enviroment:
Ubuntu 20.04
fprintd: the latest version 1.94.2. The commit id:eeaacececf6ebbc3437594ee883bfc459a735a4e
libfprint: the latest version from source code 1.94.5. Commit id: 89509c76f4a533217088607e1f0822510fe97859
Process: After enroll being finished, just locking desktop and unlocking. After once try to unlock the desktop, the swipe tip in UI is disppeared.
The coredump file is showed in accessories.
The coredump log:
sudo coredumpctl debug
[sudo] password for fpc:
PID: 4226 (fprintd)
UID: 0 (root)
GID: 0 (root)
Signal: 11 (SEGV)
Timestamp: Thu 2022-12-01 15:56:02 CST (49min ago)
Command Line: /usr/libexec/fprintd
Executable: /usr/libexec/fprintd
Control Group: /system.slice/fprintd.service
Unit: fprintd.service
Slice: system.slice
Boot ID: f9460de1a8964a238e8ae899957adccd
Machine ID: 0252132ffeed4a51a2b3be537afa1e9e
Hostname: fpc20
Storage: /var/lib/systemd/coredump/core.fprintd.0.f9460de1a8964a238e8ae899957adccd.4226.1669881362000000000000.lz4
Message: Process 4226 (fprintd) of user 0 dumped core.
Stack trace of thread 4226:
#0 0x00007f87ae77762d g_slice_alloc (libglib-2.0.so.0 + 0x7062d)
#1 0x00007f87ae77851a g_slist_prepend (libglib-2.0.so.0 + 0x7151a)
#2 0x00007f87ae4df69c n/a (libgobject-2.0.so.0 + 0x1969c)
#3 0x00007f87ae4e0728 n/a (libgobject-2.0.so.0 + 0x1a728)
#4 0x00007f87ae4e2378 g_object_new_valist (libgobject-2.0.so.0 + 0x1c378)
#5 0x00007f87ae4e26cd g_object_new (libgobject-2.0.so.0 + 0x1c6cd)
#6 0x00007f87ab5e10c6 fp_print_deserialize (libfprint-2.so.2 + 0x110c6)
#7 0x000055ecf7624a82 load_from_file (fprintd + 0x11a82)
#8 0x000055ecf76265e3 load_user_prints (fprintd + 0x135e3)
#9 0x000055ecf7626694 load_all_prints (fprintd + 0x13694)
#10 0x000055ecf762a418 fprint_device_enroll_start (fprintd + 0x17418)
#11 0x00007f87ab255ff5 n/a (libffi.so.7 + 0x6ff5)
#12 0x00007f87ab25540a n/a (libffi.so.7 + 0x640a)
#13 0x00007f87ae4db30d g_cclosure_marshal_generic (libgobject-2.0.so.0 + 0x1530d)
#14 0x00007f87ae4da802 g_closure_invoke (libgobject-2.0.so.0 + 0x14802)
#15 0x00007f87ae4edf96 n/a (libgobject-2.0.so.0 + 0x27f96)
#16 0x00007f87ae4f8a57 g_signal_emitv (libgobject-2.0.so.0 + 0x32a57)
#17 0x000055ecf762193c _fprint_dbus_device_skeleton_handle_method_call (fprintd + 0xe93c)
#18 0x00007f87ae64d92b n/a (libgio-2.0.so.0 + 0x12792b)
#19 0x00007f87ae75904e g_main_context_dispatch (libglib-2.0.so.0 + 0x5204e)
#20 0x00007f87ae759400 n/a (libglib-2.0.so.0 + 0x52400)
#21 0x00007f87ae7596f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3)
#22 0x000055ecf761dec8 main (fprintd + 0xaec8)
#23 0x00007f87ab3bd083 __libc_start_main (libc.so.6 + 0x24083)
#24 0x000055ecf761e15e _start (fprintd + 0xb15e)
Stack trace of thread 4403:
#0 0x00007f87ab4b173d syscall (libc.so.6 + 0x11873d)
#1 0x00007f87ae7a6746 g_cond_wait_until (libglib-2.0.so.0 + 0x9f746)
#2 0x00007f87ae729581 n/a (libglib-2.0.so.0 + 0x22581)
#3 0x00007f87ae7834ca n/a (libglib-2.0.so.0 + 0x7c4ca)
#4 0x00007f87ae782ad1 n/a (libglib-2.0.so.0 + 0x7bad1)
#5 0x00007f87ab593609 start_thread (libpthread.so.0 + 0x8609)
#6 0x00007f87ab4b8133 __clone (libc.so.6 + 0x11f133)
Stack trace of thread 4228:
#0 0x00007f87ab4ab99f __GI___poll (libc.so.6 + 0x11299f)
#1 0x00007f87ae75936e n/a (libglib-2.0.so.0 + 0x5236e)
#2 0x00007f87ae7596f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3)
#3 0x00007f87ae644f8a n/a (libgio-2.0.so.0 + 0x11ef8a)
#4 0x00007f87ae782ad1 n/a (libglib-2.0.so.0 + 0x7bad1)
#5 0x00007f87ab593609 start_thread (libpthread.so.0 + 0x8609)
#6 0x00007f87ab4b8133 __clone (libc.so.6 + 0x11f133)
Stack trace of thread 4227:
#0 0x00007f87ab4ab99f __GI___poll (libc.so.6 + 0x11299f)
#1 0x00007f87ae75936e n/a (libglib-2.0.so.0 + 0x5236e)
#2 0x00007f87ae7594a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3)
#3 0x00007f87ae7594f1 n/a (libglib-2.0.so.0 + 0x524f1)
#4 0x00007f87ae782ad1 n/a (libglib-2.0.so.0 + 0x7bad1)
#5 0x00007f87ab593609 start_thread (libpthread.so.0 + 0x8609)
#6 0x00007f87ab4b8133 __clone (libc.so.6 + 0x11f133)
Stack trace of thread 4230:
#0 0x00007f87ab4ab99f __GI___poll (libc.so.6 + 0x11299f)
#1 0x00007f87aaf4340d n/a (libusb-1.0.so.0 + 0xa40d)
#2 0x00007f87aaf4465c libusb_handle_events_timeout_completed (libusb-1.0.so.0 + 0xb65c)
#3 0x00007f87ab24376e n/a (libgusb.so.2 + 0x676e)
#4 0x00007f87ae782ad1 n/a (libglib-2.0.so.0 + 0x7bad1)
#5 0x00007f87ab593609 start_thread (libpthread.so.0 + 0x8609)
#6 0x00007f87ab4b8133 __clone (libc.so.6 + 0x11f133)
Stack trace of thread 4229:
#0 0x00007f87ab4ab99f __GI___poll (libc.so.6 + 0x11299f)
#1 0x00007f87aaf4a1a2 n/a (libusb-1.0.so.0 + 0x111a2)
#2 0x00007f87ab593609 start_thread (libpthread.so.0 + 0x8609)
#3 0x00007f87ab4b8133 __clone (libc.so.6 + 0x11f133)
sudo gdb /usr/libexec/fprintd
core.fprintd.0.f9460de1a8964a238e8ae899957adccd.4226.1669881362000000000000
```
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04.1) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/libexec/fprintd...
[New LWP 4226]
[New LWP 4403]
[New LWP 4228]
[New LWP 4227]
[New LWP 4230]
[New LWP 4229]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/libexec/fprintd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f87ae77762d in g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
[Current thread is 1 (Thread 0x7f87aad72180 (LWP 4226))]
(gdb) bt full
#0 0x00007f87ae77762d in g_slice_alloc () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00007f87ae77851a in g_slist_prepend () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f87ae4df69c in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3 0x00007f87ae4e0728 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4 0x00007f87ae4e2378 in g_object_new_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5 0x00007f87ae4e26cd in g_object_new () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6 0x00007f87ab5e10c6 in fp_print_deserialize (data=<optimized out>, length=<optimized out>, error=error@entry=0x7ffea0189a30) at ../libfprint/fp-print.c:877
fp_data = 0x55ecf8179520
result = 0x0
raw_value = 0x55ecf815f760
value = 0x55ecf815f760
print_data = 0x55ecf8144960
date = 0x0
aligned_data = <optimized out>
finger_int8 = 4 '\004'
finger = FP_FINGER_LEFT_RING
username = 0x55ecf8182520 "fpc"
description = 0x55ecf817af50 "FP1-20221201-4-6CD8FF28-fpc"
julian_date = 738490
type = FPI_PRINT_RAW
driver = 0x55ecf8185cf4 "fpcmoc"
device_id = 0x55ecf8185cfb "0"
device_stored = 1
__func__ = "fp_print_deserialize"
#7 0x000055ecf7624a82 in load_from_file (print=<synthetic pointer>, path=0x55ecf81822c0 "/var/lib/fprint/fpc/fpcmoc/0/4") at ../src/file_storage.c:191
err = 0x0
length = 100
contents = 0x55ecf816d380 "FP3\001"
new = <optimized out>
path = 0x55ecf81822c0 "/var/lib/fprint/fpc/fpcmoc/0/4"
base_store = 0x55ecf8182570 "/var/lib/fprint/fpc"
new = 0x0
r = <optimized out>
#8 file_storage_print_data_load (dev=0x55ecf8170190, finger=FP_FINGER_LEFT_RING, username=0x55ecf8169060 "fpc", print=0x7ffea0189aa0) at ../src/file_storage.c:217
path = 0x55ecf81822c0 "/var/lib/fprint/fpc/fpcmoc/0/4"
base_store = 0x55ecf8182570 "/var/lib/fprint/fpc"
new = 0x0
r = <optimized out>
#9 0x000055ecf76265e3 in load_user_prints (rdev=rdev@entry=0x55ecf81728e0, username=0x55ecf8169060 "fpc") at ../src/device.c:1209
print = 0x0
res = 0x7f879c002340
fingers = 0x55ecf816fd20
priv = 0x55ecf8172820
l = Python Exception <class 'gdb.MemoryError'> Cannot access memory at address 0x8:
#10 0x000055ecf7626694 in load_all_prints (rdev=rdev@entry=0x55ecf81728e0) at ../src/device.c:1235
username = <optimized out>
prints = <optimized out>
res = 0x7f8794003ce0
user = 0x55ecf816fb90 = {0x55ecf8169060}
users = 0x55ecf816fb90 = {0x55ecf8169060}
i = <optimized out>
#11 0x000055ecf762a418 in fprint_device_enroll_start (dbus_dev=0x55ecf81728e0, invocation=0x7f87880039e0, finger_name=<optimized out>) at ../src/device.c:2225
all_prints = <optimized out>
error = 0x0
existing_print = 0x0
session = 0x55ecf816d940
rdev = 0x55ecf81728e0
priv = <optimized out>
finger = <optimized out>
#12 0x00007f87ab255ff5 in () at /lib/x86_64-linux-gnu/libffi.so.7
#13 0x00007f87ab25540a in () at /lib/x86_64-linux-gnu/libffi.so.7
#14 0x00007f87ae4db30d in g_cclosure_marshal_generic () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#15 0x00007f87ae4da802 in g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
--Type <RET> for more, q to quit, c to continue without paging--
#16 0x00007f87ae4edf96 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x00007f87ae4f8a57 in g_signal_emitv () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x000055ecf762193c in _fprint_dbus_device_skeleton_handle_method_call
(connection=<optimized out>, sender=<optimized out>, object_path=<optimized out>, interface_name=0x7f879c010990 "net.reactivated.Fprint.Device", method_name=0x7f879c013bd0 "EnrollStart", parameters=<optimized out>, invocation=0x7f87880039e0, user_data=0x55ecf81728e0) at src/fprintd-dbus-interactive.c:2995
skeleton = <optimized out>
info = <optimized out>
iter = {x = {94476262878720, 1, 1, 0, 140220723157312, 140220079028704, 94476262826976, 3579507750, 140220079028704, 94476262826976, 94476251043712, 94476262823104, 140220280356864, 31, 140220414594784, 140220724379282}}
child = 0x0
paramv = 0x55ecf816b480
num_params = <optimized out>
n = <optimized out>
signal_id = 29
return_value = Python Exception <class 'ValueError'> Variable 'static_fundamental_type_nodes' not found.:
{g_type = , data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}}
__func__ = "_fprint_dbus_device_skeleton_handle_method_call"
#19 0x00007f87ae64d92b in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
#20 0x00007f87ae75904e in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f87ae759400 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007f87ae7596f3 in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x000055ecf761dec8 in main (argc=<optimized out>, argv=<optimized out>) at ../src/main.c:220
context = 0x55ecf8141350
loop = 0x55ecf815fa30
error = 0x0
manager = 0x55ecf8151a80
connection = 0x55ecf8152040
request_name_ret = 1
(gdb) q
```https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/144fprintd crash with external storage module2022-10-14T13:56:53ZZoltán Böszörményifprintd crash with external storage moduleHi,
we have an external storage module for fprintd that puts the fingerprint binary into a database. (`fprintd.service` is patched so network access is allowed.)
The problem is that while the storage module was working with `fprintd` 0...Hi,
we have an external storage module for fprintd that puts the fingerprint binary into a database. (`fprintd.service` is patched so network access is allowed.)
The problem is that while the storage module was working with `fprintd` 0.9 and 1.90.1 (with conditional compilation for the API differences), it doesn't work with the latest version.
The crash is actually inside `fprintd` when running `fprintd-enroll`. The call to `print_data_load` in our module occurs and returns `-ENOENT` for a currently non-existing print. No other call happens to other exported functions in our module. The crash dump is logged by systemd-journald:
```
Stack trace of thread 94636:
#0 0x0000000000000000 n/a (n/a + 0x0)
#1 0x00007f838839b746 ffi_call_unix64 (libffi.so.8 + 0x7746)
#2 0x00007f83883984d2 ffi_call_int.lto_priv.0 (libffi.so.8 + 0x44d2)
#3 0x00007f838850cfd3 g_cclosure_marshal_generic (libgobject-2.0.so.0 + 0x19fd3)
#4 0x00007f8388506db0 g_closure_invoke (libgobject-2.0.so.0 + 0x13db0)
#5 0x00007f8388533605 signal_emit_unlocked_R.isra.0 (libgobject-2.0.so.0 + 0x40605)
#6 0x000055562d06044b _fprint_dbus_device_skeleton_handle_method_call (fprintd + 0xd44b)
#7 0x00007f83886715d1 dispatch_invoke_in_context_func (libgio-2.0.so.0 + 0x11f5d1)
#8 0x00007f838877e4cb g_idle_dispatch (libglib-2.0.so.0 + 0x514cb)
#9 0x00007f8388781faf g_main_context_dispatch (libglib-2.0.so.0 + 0x54faf)
#10 0x00007f83887d72c8 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xaa2c8)
#11 0x00007f83887816cf g_main_loop_run (libglib-2.0.so.0 + 0x546cf)
#12 0x000055562d05ee88 main (fprintd + 0xbe88)
#13 0x00007f8385029550 __libc_start_call_main (libc.so.6 + 0x29550)
#14 0x00007f8385029609 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x29609)
#15 0x000055562d05f335 _start (fprintd + 0xc335
```
I suspect that there may be a problem in the DBus XML files that are used to generate DBus communication sources.
The function `_fprint_dbus_device_skeleton_handle_method_call` is in the generated sources.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/140fprintd can't compatiable with fingerprint enrolled by windows OS2022-08-23T17:10:36ZJohnny Lifprintd can't compatiable with fingerprint enrolled by windows OSWe found the issue of fprintd can't compatiable with fingerprint enrolled by windows OS.
reproduction step:
step1: enroll 5 fingers in windows OS, and enroll 5 finger in ubuntu OS(libfprint)
step2: contune to enroll a finger, and MOC ...We found the issue of fprintd can't compatiable with fingerprint enrolled by windows OS.
reproduction step:
step1: enroll 5 fingers in windows OS, and enroll 5 finger in ubuntu OS(libfprint)
step2: contune to enroll a finger, and MOC library will return error code to fprintd(FP_DEVICE_ERROR_DATA_FULL)
step3: fprintd will remove the finger not enrolled by ubuntu(enrolled by windows OS)
expected result:
show fingerprint is full in MOC
actul result:
windows fingerprint is removed by fprintd
Thanks.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/136Dell Fingerprint Driver - Enroll result: enroll-unknown-error2022-05-30T05:40:54ZJared SmithDell Fingerprint Driver - Enroll result: enroll-unknown-errorFailed to enroll ERROR libfprint-2-tod1-goodix driver 0.0.6
Currently running PopOs on my XPS 9310
Kernel version 5.17.5-76051705-generic.
fprintd version 1.94.2-1
libfprint-2tod1-goodix vershion 0.0.6
Jared@pop-os:~$ fprintd-enro...Failed to enroll ERROR libfprint-2-tod1-goodix driver 0.0.6
Currently running PopOs on my XPS 9310
Kernel version 5.17.5-76051705-generic.
fprintd version 1.94.2-1
libfprint-2tod1-goodix vershion 0.0.6
Jared@pop-os:~$ fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-unknown-error
I was able to get the device to work on ZorinOS but running popos with everything fully updated I received enroll-unknown-error after placing my finger on the scanner.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/135dbus tests fail with org.freedesktop.DBus.Error.InvalidArgs error2022-06-22T09:25:45ZKonstantin Lepikhovdbus tests fail with org.freedesktop.DBus.Error.InvalidArgs errorHello!
I'm trying to build 1.94.2 but can't get tests working in our build env. More interesting, they worked in 1.94.1.
The error is more or less the same:
```
526/531 fprintd:PAM+test_pam_fprintd+TestPamFprintd / TestPamFprintd.test_...Hello!
I'm trying to build 1.94.2 but can't get tests working in our build env. More interesting, they worked in 1.94.1.
The error is more or less the same:
```
526/531 fprintd:PAM+test_pam_fprintd+TestPamFprintd / TestPamFprintd.test_pam_fprintd_no_fingers_while_verifying FAIL 0.44s exit status 1
>>> PAM_WRAPPER=1 PAM_WRAPPER_DEBUGLEVEL=2 G_SLICE=always-malloc TOPSRCDIR=/usr/src/RPM/BUILD/fprintd-1.94.2 TOPBUILDDIR=/usr/src/RPM/BUILD/fprintd-1.94.2/x86_64-alt-linux PAM_WRAPPER_SERVICE_DIR=/usr/src/RPM/BUILD/fprintd-1.94.2/x86_64-alt-linux/tests/pam/services G_DEBUG=fatal-warnings MALLOC_CHECK_=2 MALLOC_PERTURB_=112 LD_PRELOAD=/usr/lib64/gcc/x86_64-alt-linux/11/../../../../lib64/libpam_wrapper.so /usr/bin/python3 /usr/src/RPM/BUILD/fprintd-1.94.2/tests/pam/test_pam_fprintd.py TestPamFprintd.test_pam_fprintd_no_fingers_while_verifying
――――――――――――――――――――――――――――――――――――― ✀ ―――――――――――――――――――――――――――――――――――――
stdout:
Using template from /usr/src/RPM/BUILD/fprintd-1.94.2/tests/dbusmock-services/fprintd.py
test_pam_fprintd_no_fingers_while_verifying (__main__.TestPamFprintd) ... ERROR
======================================================================
ERROR: test_pam_fprintd_no_fingers_while_verifying (__main__.TestPamFprintd)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/usr/src/RPM/BUILD/fprintd-1.94.2/tests/pam/test_pam_fprintd.py", line 183, in test_pam_fprintd_no_fingers_while_verifying
self.setup_device()
File "/usr/src/RPM/BUILD/fprintd-1.94.2/tests/pam/test_pam_fprintd.py", line 89, in setup_device
device_path = self.obj_fprintd_mock.AddDevice('FDO Trigger Finger Laser Reader', 3, 'swipe')
File "/usr/lib64/python3/site-packages/dbus/proxies.py", line 141, in __call__
return self._connection.call_blocking(self._named_service,
File "/usr/lib64/python3/site-packages/dbus/connection.py", line 652, in call_blocking
reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.InvalidArgs: Invalid arguments: More items found in D-Bus signature than in Python arguments
----------------------------------------------------------------------
Ran 1 test in 0.299s
FAILED (errors=1)
stderr:
PWRAP_DEBUG[<unknown> (109339)] - pwrap_init: Initialize pam_wrapper
PWRAP_DEBUG[<unknown> (109339)] - copy_confdir: Copy config files from /usr/src/RPM/BUILD/fprintd-1.94.2/x86_64-alt-linux/tests/pam/services to /tmp/pam.u
PWRAP_DEBUG[<unknown> (109339)] - pwrap_init: Successfully initialized pam_wrapper
PWRAP_DEBUG[<unknown> (109341)] - pwrap_init: Initialize pam_wrapper
PWRAP_DEBUG[<unknown> (109341)] - copy_confdir: Copy config files from /usr/src/RPM/BUILD/fprintd-1.94.2/x86_64-alt-linux/tests/pam/services to /tmp/pam.1
PWRAP_DEBUG[<unknown> (109341)] - pwrap_init: Successfully initialized pam_wrapper
PWRAP_DEBUG[<unknown> (109344)] - pwrap_init: Initialize pam_wrapper
PWRAP_DEBUG[<unknown> (109344)] - copy_confdir: Copy config files from /usr/src/RPM/BUILD/fprintd-1.94.2/x86_64-alt-linux/tests/pam/services to /tmp/pam.4
PWRAP_DEBUG[<unknown> (109344)] - pwrap_init: Successfully initialized pam_wrapper
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――
```
I've tried to look into similar errors but can't find anything meaningful, maybe dbus is not running? But I guess it's not needed in mock environment.
Full build log attached.[build.log.tmp](/uploads/b42f4ea68a48998810b4c610f3e82a29/build.log.tmp)
Thanks!https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/134Protocol error with 04f3:0c282022-05-01T16:00:07ZMatt BarnardProtocol error with 04f3:0c28I'm having trouble with my newly bought 04f3:0c28 Elan Microelectronics Corp. fingerprint sensor [FeinTech FPS00200]. The device disconnects with gnome settings and with fprintd-enroll. I'd appreciate any advice in getting it working. If...I'm having trouble with my newly bought 04f3:0c28 Elan Microelectronics Corp. fingerprint sensor [FeinTech FPS00200]. The device disconnects with gnome settings and with fprintd-enroll. I'd appreciate any advice in getting it working. If there's any further information I need to provide please let me know.
This is the log I get:
```
$ journalctl -f -u fprintd.service
May 01 12:54:59 fedora systemd[1]: fprintd.service: Deactivated successfully.
May 01 13:02:07 fedora systemd[1]: Starting Fingerprint Authentication Daemon...
May 01 13:02:07 fedora systemd[1]: Started Fingerprint Authentication Daemon.
May 01 13:02:32 fedora fprintd[3721]: Failed to clear storage before first enrollment: Device has no storage.
May 01 13:02:56 fedora fprintd[3721]: Device reported an error during enroll: The driver encountered a protocol error with the device.
```
And this is what it says in enrollment:
```
$ fprintd-enroll --finger left-index-finger myusername
Using device /net/reactivated/Fprint/Device/0
Enrolling left-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-disconnected
```
I'm using Fedora 35 on a Lenovo Yoga 510-14ISK with GNOME 41.
Libpfrint version:
```
Name : libfprint
Version : 1.94.3
Release : 1.fc35
Architecture : x86_64
```
Fprintd version:
```
Name : fprintd
Version : 1.94.1
Release : 1.fc35
```https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/133[Request] Meson option to disable tests2022-05-06T09:07:19ZAdrian Vovkadrianvovk@gmail.com[Request] Meson option to disable testsIt would be nice if there was an option that could be passed (`-Dtests=false`) to disable tests. These tests just won't work in some build environments, and there's really not much point packaging the dependencies of the tests (dbusmock,...It would be nice if there was an option that could be passed (`-Dtests=false`) to disable tests. These tests just won't work in some build environments, and there's really not much point packaging the dependencies of the tests (dbusmock, dbus-daemon, pam_wrapper, etc) just to satisfy meson and throw them out immediately afterhttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues/132Confused, official documentation states USB device 04F3:0C3D supported? But ...2022-03-30T15:40:29ZJibun-no-KageConfused, official documentation states USB device 04F3:0C3D supported? But fprintd service reports "No driver found for USB device 04F3:0C3D"Confused, official documentation states USB device 04F3:0C3D supported? But fprintd service reports "No driver found for USB device 04F3:0C3D" Running on Debian 11 fully updated as of date of this post.
`# lsusb|grep -i fingerprint
ii...Confused, official documentation states USB device 04F3:0C3D supported? But fprintd service reports "No driver found for USB device 04F3:0C3D" Running on Debian 11 fully updated as of date of this post.
`# lsusb|grep -i fingerprint
ii fprintd 1.90.9-1 amd64 D-Bus daemon for fingerprint reader access
ii libfprint-2-2:amd64 1:1.90.7-2 amd64 async fingerprint library of fprint project, shared libraries
`
If I compile the latest fprintd and libfprint, is that going to change the situation? Clearly something is off, with the 1.90* versions, because the service keeps dying. Starts only to stop when trying to enroll.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/131138a:0097 Validity Sensors2022-03-23T09:02:40ZNathan138a:0097 Validity SensorsI can has device support plz?
138a:0097 Validity Sensors
-NateI can has device support plz?
138a:0097 Validity Sensors
-Natehttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues/128Need support for ELAN1300:00 04F3:3104 Touchpad2021-12-21T13:50:35ZAmirhosein BaratiNeed support for ELAN1300:00 04F3:3104 TouchpadAsus K510
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available1
Tnx.Asus K510
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available1
Tnx.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/127Driver request: FPC Sensor Controller2022-03-10T10:04:03ZDimaDriver request: FPC Sensor ControllerI have a Xiaomi notebook pro x (2021). And it is shiped with
`Bus 003 Device 003: ID 10a5:9200 FPC FPC Sensor Controller` which is not recognized for now.
So I humbly ask to support this device.I have a Xiaomi notebook pro x (2021). And it is shiped with
`Bus 003 Device 003: ID 10a5:9200 FPC FPC Sensor Controller` which is not recognized for now.
So I humbly ask to support this device.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/126fprintd does net delete stale fingerprint after install Linux distribution again2021-12-27T12:19:05ZAndy Chifprintd does net delete stale fingerprint after install Linux distribution againHi, I have a goodix fingerprint device on my laptop [27c6:63ac]. The fingerprint device does not have problem at first place, after I re-install OS again, it can't enroll fingerprint successfully. I have to use this python script to dele...Hi, I have a goodix fingerprint device on my laptop [27c6:63ac]. The fingerprint device does not have problem at first place, after I re-install OS again, it can't enroll fingerprint successfully. I have to use this python script to delete stored fingerprint (https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/415).
```
fprintd version: 1.94.1
libfprint version: 1.94.1
```
[fprintd.log](/uploads/d163ccdbd7c037ac5fcbdb70113db07a/fprintd.log)https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/125Framework Laptop - Goodix ID: 27c6:609c - Not detected as reader2022-01-24T16:16:58ZfattminerFramework Laptop - Goodix ID: 27c6:609c - Not detected as readerHey,
On my framework with the aforementioned Goodix ID: 27c6:609c, with the newest fprintd and libfprint in EndeavourOS (arch) it will not detect the reader as a reader. It will detect it as a 'USB2.0 MISC' but not as a fingerprint read...Hey,
On my framework with the aforementioned Goodix ID: 27c6:609c, with the newest fprintd and libfprint in EndeavourOS (arch) it will not detect the reader as a reader. It will detect it as a 'USB2.0 MISC' but not as a fingerprint reader. Seems like a common issue on the framework laptop.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/124Need support for 04f3:0c4b2021-12-02T11:01:21ZXelXenNeed support for 04f3:0c4bLemme know if i can help you out with extracting info for 04f3:0c4bLemme know if i can help you out with extracting info for 04f3:0c4bhttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues/123translations out of date2021-12-02T09:56:25Ztheinrich88translations out of dateDue to changes in original messages with this commit b483edbe .Due to changes in original messages with this commit b483edbe .