fprintd issueshttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues2020-02-14T15:09:10Zhttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues/1Fprintd-enroll should maybe show some info or feedback when fingerprints are ...2020-02-14T15:09:10ZBugzilla Migration UserFprintd-enroll should maybe show some info or feedback when fingerprints are entered.## Submitted by goldie
**[Link to original bug (#79723)](https://bugs.freedesktop.org/show_bug.cgi?id=79723)**
## Description
Fprintd-enroll could tell user that it expects multiple scans. Since the message after first scan is somet...## Submitted by goldie
**[Link to original bug (#79723)](https://bugs.freedesktop.org/show_bug.cgi?id=79723)**
## Description
Fprintd-enroll could tell user that it expects multiple scans. Since the message after first scan is something like "Success" users might think that that's all, and quit or just wait for the program to quit, and therefore fail to actually enter any fingerprint data.
https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/4Port API docs to gdbus-codegen2020-11-26T11:20:09ZBugzilla Migration UserPort API docs to gdbus-codegen## Submitted by Bastien Nocera
**[Link to original bug (#90594)](https://bugs.freedesktop.org/show_bug.cgi?id=90594)**
## Description
When we've ported most of the code to GDBus, we can start using gdbus-codegen to create the gtk-do...## Submitted by Bastien Nocera
**[Link to original bug (#90594)](https://bugs.freedesktop.org/show_bug.cgi?id=90594)**
## Description
When we've ported most of the code to GDBus, we can start using gdbus-codegen to create the gtk-doc docbook.
See https://github.com/hadess/iio-sensor-proxy/ for an examplehttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues/23Better default policies2020-11-12T12:31:40ZBastien NoceraBetter default policiesThe PAM module should not allow authentication if:
- the user's password has never been entered
- a certain amount of time has passed since the last authentication (fingerprint or not)
- after a certain amount of failures to unlock with ...The PAM module should not allow authentication if:
- the user's password has never been entered
- a certain amount of time has passed since the last authentication (fingerprint or not)
- after a certain amount of failures to unlock with the fingerprint
It is possible that this should be implemented at a higher level, such as in GDM directly, but that would leave the console with the same "weaker" security.
CC @halflinehttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues/41[Request] OpenRC Support2023-02-13T14:44:07ZFlyingWaffle[Request] OpenRC SupportAlthough fprintd has always "required" systemd to function, disabling checks for it has allowed fprintd to function on systems running OpenRC instead. Since the d70f15b5 commit switching to sd-bus this has no longer been possible. (On ...Although fprintd has always "required" systemd to function, disabling checks for it has allowed fprintd to function on systems running OpenRC instead. Since the d70f15b5 commit switching to sd-bus this has no longer been possible. (On Gentoo at least, there is no way to isolate sd-bus into libsystemd and run without full systemd.)
I'd like to request support for OpenRC if that is in any way possible.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/45Please make the build-dependency for the tests optional2022-05-24T11:44:25ZLaurent BigonvillePlease make the build-dependency for the tests optionalHello,
It would be nice if the build-dependencies for tests were made optional with a "test(s)" flag passed to meson
ThanksHello,
It would be nice if the build-dependencies for tests were made optional with a "test(s)" flag passed to meson
Thankshttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues/85New D-Bus APIs (or API additions)2021-02-05T18:00:26ZMarco TrevisanNew D-Bus APIs (or API additions)We had some preliminary discussions with @benzea about various dbus API additions we would need, so trying to get an incomplete and to-be-updated list here (feel free to edit this comment to add whatever you think is needed).
In the dev...We had some preliminary discussions with @benzea about various dbus API additions we would need, so trying to get an incomplete and to-be-updated list here (feel free to edit this comment to add whatever you think is needed).
In the device scope:
- [ ] Add `supports-identification` property and `IdentifyFingerStart/IdentifyFingerStop` methods
- It will be used by the enroll / prints manager dialog to identify the finger so that
the user can test the enrolled fingers
- Will be used by the login screen so that can be "swipe any finger"
- [ ] ~~Add `SetPreferredFinger` for devices with no identification support~~
- ~~So that the user can select the preferred finger to be used at verification phase when there's no user interaction (i.e. at login screen)~~
- This could be just done by making the UI not accepting more than one print, and the cmd-line tools to warn
- [ ] Add `DeleteEnrolledFinger` method
- Manage prints UI [dialog design](https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18) should allow to remove a single print
- [ ] Add `finger-on-sensor` property:
- Enroll dialog should highlight the finger when the sensor is touched during enrollment
- [GNOME shell unlock dialog](https://gitlab.gnome.org/Teams/Design/os-mockups/-/issues/56) should highlight the fingerprint icon when user has a finger on it
- [ ] Make fingerprints to have a customized label (this was a design request, not sure fprintd should handle it)
- [x] Device `added`/`removed` signalling on hotplugging (this is somewhat already handled as we're going to use an object manager)
- [ ] Device `available` property to provide dummy devices for print listing/deletion if devices are currently unplugged.
- [ ] A generic Manager's `Identify` method that will identify any user on any device (to allow login without having to select an user name).
TODO:
* Do we need new API for libfprint#256 (device initiated resume with immediate verify)
Most of the required things here can be just added, and in case clients can handle the `DBus.Error.UnknownMethod` in case (even without bothering adding a different interface IMHO), however...
Given that now we're almost past the gdbus port, we were also considering the idea that maybe we could just refactor the whole DBus API (maybe putting it into the FDO namespace, at this point).
I'd imagine a such iface would imply that when we start a device action, we return an object that can be used to stop the operation and get notified about the results of it.
Maybe something like this (was quickly drafted, so I might have forgot things):
```xml
<!DOCTYPE node PUBLIC
"-//freedesktop//DTD D-BUS Object Introspection 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd" >
<node xmlns:doc="http://www.freedesktop.org/dbus/1.0/doc.dtd">
<interface name="org.freedesktop.Fprintd1.Manager">
<!-- No need to implement get devices, as it will be handled by the object manager -->
<method name="GetDefaultDevice">
<arg type="o" name="device" direction="out" />
</method>
</interface>
<interface name="org.freedesktop.Fprintd1.Device">
<method name="Claim">
<arg type="s" name="username" direction="in" />
<arg type="o" name="claimed_device" direction="out" />
</method>
</interface>
<interface name="org.freedesktop.Fprintd1.ClaimedDevice">
<method name="Enroll">
<arg type="s" name="finger_name" direction="in" />
<arg type="o" name="enroll_action" direction="out" />
</method>
<method name="Verify">
<arg type="s" name="finger_name" direction="in" />
<arg type="o" name="verify_action" direction="out" />
</method>
<method name="Release" />
</interface>
<interface name="org.freedesktop.Fprintd1.EnrollAction">
<!-- Maybe move this to a more generic DeviceAction interface -->
<method name="Stop" />
<property name="enroll-status" type="s" access="read" />
<signal name="done">
<arg type="b" name="done" />
</signal>
</interface>
<interface name="org.freedesktop.Fprintd1.VerifyAction">
<!-- Maybe move this to a more generic DeviceAction interface -->
<method name="Stop" />
<property name="selected-finger" type="s" access="read" />
<property name="verify-status" type="s" access="read" />
</interface>
</node>
```2.0https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/129Device removal idle handler can race with next dbus request2022-02-24T16:28:41ZBenjamin BergDevice removal idle handler can race with next dbus requestThe `test_removal_during_enroll` is flaky, because the internal machinery to remove he device may not yet be finished when the next `GetDevices` request comes in.
This might need to be fixed in libfprint itself, to run device removal wi...The `test_removal_during_enroll` is flaky, because the internal machinery to remove he device may not yet be finished when the next `GetDevices` request comes in.
This might need to be fixed in libfprint itself, to run device removal with a higher priority. i.e. `remove_device_idle_cb` in `fp-context.c`.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/130Use/Create PAM extension for better UI support2022-03-05T10:58:24ZBenjamin BergUse/Create PAM extension for better UI supportGDM has support for extensions. They work by setting an environment variable. Each extension enabled extension gets a type, and then binary messages can be send.
Using this, we can replace the string prompts with proper status reporting...GDM has support for extensions. They work by setting an environment variable. Each extension enabled extension gets a type, and then binary messages can be send.
Using this, we can replace the string prompts with proper status reporting. Maybe, we should just define a json type or so, and then send json strings?
Note that right now this is only used by SSSD to create drop-down selections.
See `gdm-pam-extensions.h` and `pam_sssd`.
----
The main goal here is to remove the need for gnome-shell to talk directly with fprintd. If the messages we implement do not solve this problem, then the whole thing would be pretty useless.Marco TrevisanMarco Trevisanhttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues/137enroll-disconnect2023-02-14T05:36:45ZRyein Goddardenroll-disconnect`Bus 003 Device 002: ID 04f3:0c11 Elan Microelectronics Corp. ELAN:Fingerprint`
```
sudo fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result:...`Bus 003 Device 002: ID 04f3:0c11 Elan Microelectronics Corp. ELAN:Fingerprint`
```
sudo fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-disconnected
sudo fprintd-enroll
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-unknown-error
```
This is my experience when trying to enroll. Happy to provide extra information needed for debugging.
This is Ubuntu 22.04
apt says package version is, fprintd/jammy,now 1.94.2-1https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/138pam: Print something when fingerprint was successfully detected2022-07-29T14:51:25ZJoachim Breitnerpam: Print something when fingerprint was successfully detectedImagine you are using `sudo` to start a long-running silent process, like in this example:
```
~ $ LANG=C sudo sleep 10
Place your right index finger on the fingerprint reader
```
After tapping the fingerprint reader, it seems there is...Imagine you are using `sudo` to start a long-running silent process, like in this example:
```
~ $ LANG=C sudo sleep 10
Place your right index finger on the fingerprint reader
```
After tapping the fingerprint reader, it seems there is no easy way of knowing if the process was started, or if the finger just wasn’t detected.
It might help if it printed
```
~ $ LANG=C sudo sleep 10
Place your right index finger on the fingerprint reader
Finger successfully recognized
```
or something like that.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/139[wish] add "touching"2022-08-20T16:11:36Zpromeneur[wish] add "touching"Hello
It is handy on smartphone to just touch the fingerprint reader, more than swapping.
Please add the ability to just touch the fingerprint reader.
ThanksHello
It is handy on smartphone to just touch the fingerprint reader, more than swapping.
Please add the ability to just touch the fingerprint reader.
Thankshttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues/141New: fingerprint authentication, always fails2022-08-28T11:29:49ZpromeneurNew: fingerprint authentication, always failsopenSUSE Tumbleweed
KDE Gears 22.08.0
login screen or lock screen, with my index or my middle finger, fingerprint
fails with errors :
- swiping is too short
or
- fingerprint is not recognized
Is there any problem with my BENSS reader ?...openSUSE Tumbleweed
KDE Gears 22.08.0
login screen or lock screen, with my index or my middle finger, fingerprint
fails with errors :
- swiping is too short
or
- fingerprint is not recognized
Is there any problem with my BENSS reader ?
fingerprint reader : usb adapter Benss (ID 04f3:0c3d Elan Microelectronics Corp. ELAN:Fingerprint)https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/142fprint authentication dialog stays displayed a too short time2023-05-23T14:14:45Zpromeneurfprint authentication dialog stays displayed a too short timeSTEPS TO REPRODUCE
1. press "enter" on the login screen or the lock screen
2. fprint dialog invites you to swipe your finger
3.
OBSERVED RESULT
During swiping my finger, the fprint dialog disappears. I can't see the result of my swipi...STEPS TO REPRODUCE
1. press "enter" on the login screen or the lock screen
2. fprint dialog invites you to swipe your finger
3.
OBSERVED RESULT
During swiping my finger, the fprint dialog disappears. I can't see the result of my swiping and the new invitation. I must type "enter"
EXPECTED RESULT
During swiping my finger, the fprint dialog does not disappear. I can see the result of my swiping and the new invitation.
The fprint dialog must not disappear until success or returning to password authentication.
I sent a report to kde team.
https://bugs.kde.org/show_bug.cgi?id=458424
Here is the answer :
This is an fprint/PAM issue. The fingerprint authentication method has a timeout and stops being active after a time. That's just the way it works. To alter this would require changes outside of the scope of KDE, either in fprint, PAM, or their configuration files.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/143Request to support device | 04f3:0c4c Elan Microelectronics Corp2022-10-07T15:16:13ZEngie TawfikRequest to support device | 04f3:0c4c Elan Microelectronics CorpHi great fprint folks!
I listed the supported devices and could see that both
| 04f3:0c4b | ElanTech Fingerprint Sensor |
|-----------|-----------------------------|
| 04f3:0c4d | ElanTech Fingerprint Sensor |
are supported but not...Hi great fprint folks!
I listed the supported devices and could see that both
| 04f3:0c4b | ElanTech Fingerprint Sensor |
|-----------|-----------------------------|
| 04f3:0c4d | ElanTech Fingerprint Sensor |
are supported but not
|-----------|-----------------------------|
| 04f3:0c4c | Elan Microelectronics Corp |
|-----------|-----------------------------|
It's on HP Envy 360, and I have seen someone else also posting about it at:
https://www.reddit.com/r/Fedora/comments/xbue8o/anyone_got_the_04f30c4c_fingerprint_reader_working/
Could you do us a favour and help us by supporting this device, please?https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/145failed to enroll with device 04f3:0c1a Elan Microelectronics Corp.2022-10-15T00:26:56ZTiger Wangfailed to enroll with device 04f3:0c1a Elan Microelectronics Corp.Logs
```
Oct 14 20:07:43 riceberry fprintd[9777]: Failed to clear storage before first enrollment: Device has no storage.
Oct 14 20:08:00 riceberry fprintd[9777]: Internal state machine issue: transition from FPI_IMAGE_DEVICE_STATE_AWAI...Logs
```
Oct 14 20:07:43 riceberry fprintd[9777]: Failed to clear storage before first enrollment: Device has no storage.
Oct 14 20:08:00 riceberry fprintd[9777]: Internal state machine issue: transition from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF should not happen!
Oct 14 20:08:11 riceberry fprintd[9777]: Device reported an error during enroll: The driver encountered a protocol error with the device.
Oct 14 20:08:15 riceberry fprintd[9777]: Failed to clear storage before first enrollment: Device has no storage.
Oct 14 20:08:21 riceberry fprintd[9777]: Device reported an error during enroll: The driver encountered a protocol error with the device.
Oct 14 20:08:39 riceberry fprintd[9777]: Failed to clear storage before first enrollment: Device has no storage.
Oct 14 20:08:48 riceberry fprintd[9777]: Device reported an error during enroll: The driver encountered a protocol error with the device.
```
Device
```
Bus 001 Device 003: ID 04f3:0c1a Elan Microelectronics Corp. ELAN:Fingerprint
```https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/146fprintd-verify always says on-match device[04f3:0c1a]2024-03-10T19:13:53Zsysytwlfprintd-verify always says on-match device[04f3:0c1a]* result:
![fprintd-verify](/uploads/3c3e90581e2a041f54c28b5b85fb385e/fprintd-verify.png)
* version:
![version](/uploads/a3cdca6702f57433d7d44065180f6934/version.png)
* I use the same finger. test within few second. The device is working...* result:
![fprintd-verify](/uploads/3c3e90581e2a041f54c28b5b85fb385e/fprintd-verify.png)
* version:
![version](/uploads/a3cdca6702f57433d7d44065180f6934/version.png)
* I use the same finger. test within few second. The device is working on windows.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/147Argument timeout=-1 or timeout=300 in pam.d config not working, and manual wa...2023-05-17T16:05:46ZBenjamin ChrisArgument timeout=-1 or timeout=300 in pam.d config not working, and manual was incorrectly edited.> Update: a merge request was opened to fix this issue: https://gitlab.freedesktop.org/libfprint/fprintd/-/merge_requests/195.
I'm using lightdm on my linux desktop, but the default 30s timeout of fprintd makes the fingerprint reading a...> Update: a merge request was opened to fix this issue: https://gitlab.freedesktop.org/libfprint/fprintd/-/merge_requests/195.
I'm using lightdm on my linux desktop, but the default 30s timeout of fprintd makes the fingerprint reading authentication on lock screen barely usable, because when I'm away and this machine is autolocked, I **must** verify my fingerprint in 30 seconds, otherwise it won't read any fingerprint anymore, and I can't do anything to make it reauthenticate again.
So I read the release log of fprintd, and found that in release [1.94.2](https://gitlab.freedesktop.org/libfprint/fprintd/-/commit/0d2e2a6742cbec847aa756da25afd4b73d9ec53f), it claims the ability to ignore timeout, which says *Add PAM module options to ignore timeout/retry limits*. But when I read the builtin manual via `man pam_fprind`, there's nowhere mention this feature.
But according to this merge request https://gitlab.freedesktop.org/libfprint/fprintd/-/merge_requests/89, the contributor indeed edit the manual. That's weird.
Nevertheless, I still try to add timeout=-1 in lightdm pam config file, but with no luck. Then I change it to timeout=300, It's not working either. However, when I change the timeout from 300 to 60 (or any number between 10 and 99), It indeed works.
With curiosity, I manage to investigate into the source code, and found the following issue:
1. https://gitlab.freedesktop.org/libfprint/fprintd/-/blob/0d2e2a6742cbec847aa756da25afd4b73d9ec53f/pam/pam_fprintd.c#L851 limits the length of `timeout` argument to only `timeout=xx`, which only accepts two digits, however the timeout variable is `unsigned static`, which ranges far more than two digits number. So any number between 10 and 99 will work, other won't.
```c
else if (str_has_prefix (argv[i], TIMEOUT_MATCH) && strlen (argv[i]) <= strlen (TIMEOUT_MATCH) + 2)
```
2. The contributor of the above merge request tried to imitate the coding style of the `max-tries` argument parsing method, which can also accept a negative number, and set the max-tries variable to `UINT_MAX`. At a glance, It must be working, but when `timeout` variable is being used, which is in https://gitlab.freedesktop.org/libfprint/fprintd/-/blob/0d2e2a6742cbec847aa756da25afd4b73d9ec53f/pam/pam_fprintd.c#L451, the `verification_end` variable is fixed to `ULONG_MAX` because `timeout` is `UINT_MAX`. Remember it's a `uint64_t`, and the following code creates a `int64_t` variable called `wait_time`. compared to 64bit integer, current usec time is a relatively small number, so assigning a uint to a int, is doomed to being a negative number, and causing the fingerprint verification process stops immediately.
```c
while (data->max_tries > 0)
{
uint64_t verification_end = ULONG_MAX;
if (timeout != UINT_MAX)
verification_end = now () + (timeout * USEC_PER_SEC);
// ...
for (;;)
{
struct signalfd_siginfo siginfo;
int64_t wait_time;
wait_time = verification_end - now ();
if (wait_time <= 0)
break;
```
3. That's obviously the issue, but why the manual lost the negative number explanation both `max-tries` and `timeout`? I tried to figure out how the manual is built, and found that in `data/` directory, the *.pod file is where to edit, it will generates the traditional unix manual page, but in this directory, a unix manual page with the same filename exists, which causes confusion. Apparently previous contributors, which respectively added `max-tries` and `timeout` ignore options, both misedited the manual file. When I try to remove these generated file, I don't see any error, so I think It's safe to just delete them, thus to prevent others from misediting manual files again.
I'm working to create a merge request fixing these issues, but It's my first time to work in freedesktop project, so feel free to give me suggesions if I did anything wrong.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/151Tests fail with GLib 2.76.02023-03-12T16:39:29ZJan TojnarTests fail with GLib 2.76.0Trying to [upgrade](https://github.com/NixOS/nixpkgs/pull/218143) GLib to 2.76.0 on NixOS, the tests started to fail with:
```
(fprintd:9047): GLib-GIO-CRITICAL **: 16:35:54.205: GTask 0x460f20 (source object: 0x45fe70, source tag: (nil...Trying to [upgrade](https://github.com/NixOS/nixpkgs/pull/218143) GLib to 2.76.0 on NixOS, the tests started to fail with:
```
(fprintd:9047): GLib-GIO-CRITICAL **: 16:35:54.205: GTask 0x460f20 (source object: 0x45fe70, source tag: (nil)) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
```
Full [testlog.txt](/uploads/106856fb4f1ad02505cfc07520525741/testlog.txt)
I have bisected it to https://gitlab.gnome.org/GNOME/glib/-/commit/fe89940572e2c01e5bb04504ba4de09bea1122a2https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/153No prints for any user2023-03-27T13:17:26ZKristoferNo prints for any user## Background
At some time in the (recent) past I tried adding fingerprint authentication for logging in, which was successful, but then it didn't work for logging in. I removed the fingerprints, or they disappeared (can't remember). Now...## Background
At some time in the (recent) past I tried adding fingerprint authentication for logging in, which was successful, but then it didn't work for logging in. I removed the fingerprints, or they disappeared (can't remember). Now, I'm trying again while debugging to file an issue.
No user on my system has prints registered:
```bash
sudo fprintd-list $(cat /etc/passwd | cut -d: -f1)
# found 1 devices
# Device at /net/reactivated/Fprint/Device/0
# Using device /net/reactivated/Fprint/Device/0
# User root has no fingers enrolled for Goodix MOC Fingerprint Sensor.
# User myusername has no fingers enrolled for Goodix MOC Fingerprint Sensor.
# User otherusername has no fingers enrolled for Goodix MOC Fingerprint Sensor.
```
## Using Gnome UI
1. Verify no fingerprint is registered (also set to "off" in Gnome menu):
```bash
sudo fprintd-list $USER
# found 1 devices
# Device at /net/reactivated/Fprint/Device/0
# Using device /net/reactivated/Fprint/Device/0
# User myusername has no fingers enrolled for Goodix MOC Fingerprint Sensor.
```
2. Attempt to register fingerprint in gnome UI
```log
Mar 27 10:42:13 myhostname systemd[1]: fprintd.service: Deactivated successfully.
Mar 27 10:49:30 myhostname systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Mar 27 10:49:31 myhostname fprintd[8514]: libusb: error [udev_hotplug_event] ignoring udev action change
Mar 27 10:49:31 myhostname systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Mar 27 10:49:31 myhostname fprintd[8514]: libusb: error [udev_hotplug_event] ignoring udev action change
Mar 27 10:50:01 myhostname systemd[1]: fprintd.service: Deactivated successfully.
Mar 27 10:51:09 myhostname systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Mar 27 10:51:09 myhostname fprintd[10191]: libusb: error [udev_hotplug_event] ignoring udev action change
Mar 27 10:51:09 myhostname systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Mar 27 10:51:09 myhostname fprintd[10191]: libusb: error [udev_hotplug_event] ignoring udev action change
Mar 27 10:51:55 myhostname fprintd[10191]: libusb: error [udev_hotplug_event] ignoring udev action change
Mar 27 10:51:55 myhostname fprintd[10191]: libusb: error [udev_hotplug_event] ignoring udev action change
Mar 27 10:52:31 myhostname fprintd[10191]: Capture sample failed, result: 0xc0
Mar 27 10:52:39 myhostname fprintd[10191]: Capture sample failed, result: 0xc0
Mar 27 10:52:44 myhostname fprintd[10191]: Device reported an error during enroll: Finger was already enrolled as 'FP1-20230301-9-66C5BA98-myusername'
Mar 27 10:58:56 myhostname fprintd[10191]: libusb: error [udev_hotplug_event] ignoring udev action change
Mar 27 10:58:56 myhostname fprintd[10191]: libusb: error [udev_hotplug_event] ignoring udev action change
Mar 27 10:59:03 myhostname fprintd[10191]: libusb: error [udev_hotplug_event] ignoring udev action change
Mar 27 10:59:03 myhostname fprintd[10191]: libusb: error [udev_hotplug_event] ignoring udev action change
```
## Enrolling on CLI
1. Verify
```bash
sudo fprintd-list $USER
# found 1 devices
# Device at /net/reactivated/Fprint/Device/0
# Using device /net/reactivated/Fprint/Device/0
# User myusername has no fingers enrolled for Goodix MOC Fingerprint Sensor.
```
2. Enroll
```bash
sudo fprintd-enroll $USER
# 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-retry-scan
# Enroll result: enroll-stage-passed
# Enroll result: enroll-stage-passed
# Enroll result: enroll-stage-passed
# Enroll result: enroll-completed
```
3. Verify
```bash
fprintd-list $USER
# found 1 devices
# Device at /net/reactivated/Fprint/Device/0
# Using device /net/reactivated/Fprint/Device/0
# Fingerprints for user myusername on Goodix MOC Fingerprint Sensor (press):
- #0: right-index-finger
```
4. Fingerprint disappeared, but when trying to reproduce the issue, it didn't disappear
5. Fingerprint verification not working
```bash
sudo fprintd-verify $USER
# 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)
```
## Versions
```bash
man fprintd | tail -n 1
# freedesktop 2022-07-21 fprintd(1)
grep PRETTY_NAME /etc/os-release
# PRETTY_NAME="Fedora Linux 37.20230319.0 (Silverblue)"
gnome-control-center --version
# gnome-control-center 43.2
```https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/154unlock fail after waking up ubuntu for 30 seconds2023-04-11T08:47:09ZGitlab FPCunlock fail after waking up ubuntu for 30 secondsubuntu22.04
fprintd version: default
device: synaptic (06cb:00df)
Step:
1. Lock Screen.
2. unlock OS with keypad and wait 30 seconds. pls move mouse to avoid OS sleeping
3. Touch the sensor. There is no reaction.
4. I think it is...ubuntu22.04
fprintd version: default
device: synaptic (06cb:00df)
Step:
1. Lock Screen.
2. unlock OS with keypad and wait 30 seconds. pls move mouse to avoid OS sleeping
3. Touch the sensor. There is no reaction.
4. I think it is not connection with the specific sensor. It's a common question in fprintd.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/155Cannot unlock with enrolled finger and no reminder:"or swipe finger" in lock ...2023-04-28T07:54:39ZGitlab FPCCannot unlock with enrolled finger and no reminder:"or swipe finger" in lock screen after reboot.ubuntu: 20.04
fprintd :default
1. reboot the desktop
2. Click unlock screen. There is no tip for swiping the finger.
3. The printd just called the probe callback. No further callback function is called by fprintd.ubuntu: 20.04
fprintd :default
1. reboot the desktop
2. Click unlock screen. There is no tip for swiping the finger.
3. The printd just called the probe callback. No further callback function is called by fprintd.https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/157USB fingerprint reader verification2023-05-10T07:39:33ZColin WallsUSB fingerprint reader verificationI bought a cheap USB fingerprint reader, which my Tumbleweed installation recognises:
[57410.112935] usb 2-1.1: new full-speed USB device number 9 using ehci-pci
[57410.222356] usb 2-1.1: New USB device found, idVendor=0483, idProduct=2...I bought a cheap USB fingerprint reader, which my Tumbleweed installation recognises:
[57410.112935] usb 2-1.1: new full-speed USB device number 9 using ehci-pci
[57410.222356] usb 2-1.1: New USB device found, idVendor=0483, idProduct=2016, bcdDevice= 0.01
[57410.222367] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[57410.222372] usb 2-1.1: Product: Biometric Coprocessor
[57410.222375] usb 2-1.1: Manufacturer: STMicroelectronics
[59577.002850] usb 2-1.1: USB disconnect, device number 9
[59611.140935] usb 2-1.1: new full-speed USB device number 10 using ehci-pci
[59611.250493] usb 2-1.1: New USB device found, idVendor=0483, idProduct=2016, bcdDevice= 0.01
[59611.250505] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[59611.250509] usb 2-1.1: Product: Biometric Coprocessor
[59611.250513] usb 2-1.1: Manufacturer: STMicroelectronics
I can enrol my fingerprint without any difficulty. However, when I try to verify my fingerprint it immediately returns without asking me to scan my print
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
- #0: right-index-finger
Verify started!
Verifying: right-index-finger
Verify result: verify-disconnected (done)
Two questions:
Can anyone tell me how I might fix the problem? Happy to provide additional information
If the answer is, “it is a crap scanner”, could anyone suggest a scanner that might work?https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/159Fingerprint suddenly stopped working (unknow error)2023-07-24T10:40:30ZPeter RiesFingerprint suddenly stopped working (unknow error)It used to work until last week - did nothing special. HW is working (BIOS and passed to a VM)
First no fingers recognized. Deleted all and tried to re-register but get the unknown error now...
Just put the right index finger on sensor...It used to work until last week - did nothing special. HW is working (BIOS and passed to a VM)
First no fingers recognized. Deleted all and tried to re-register but get the unknown error now...
Just put the right index finger on sensor once -> error.
Environment
```
Operating System: EndeavourOS
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.1.39-1-lts (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics
Memory: 30.6 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 20UES00L00
System Version: ThinkPad T14 Gen 1
```
Fingerprintreader
```
❯ lsusb
...
Bus 006 Device 002: ID 06cb:00bd Synaptics, Inc. Prometheus MIS Touch Fingerprint Reader
...
```
Logs
```
❯ sudo env G_MESSAGES_DEBUG=all /usr/lib/fprintd -t
(fprintd:5265): GLib-GIO-DEBUG: 09:25:35.673: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
(fprintd:5265): fprintd-DEBUG: 09:25:35.675: About to load configuration file '/etc/fprintd.conf'
(fprintd:5265): fprintd-DEBUG: 09:25:35.675: Launching FprintObject
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.675: Initializing FpContext (libfprint version 1.94.4)
(fprintd:5265): fprintd-DEBUG: 09:25:35.691: Preparing devices for resume
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 1D6B:0003
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 8087:0029
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 1D6B:0002
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 0BDA:8153
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 0424:5906
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 1D6B:0003
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 0424:284C
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 413C:301D
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 041E:40A0
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 0B0E:1113
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 2109:2812
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 0424:2906
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 1D6B:0002
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 1D6B:0003
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 04F2:B6D0
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 1D6B:0002
(fprintd:5265): libfprint-context-DEBUG: 09:25:35.692: No driver found for USB device 1D6B:0002
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:35.696: 1033142209: ../libfprint/libfprint/drivers/synaptics/synaptics.c:1231
(fprintd:5265): fprintd-DEBUG: 09:25:35.806: Got delay inhibitor for sleep.
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:35.806: Build Time: 1629962591
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:35.806: Build Num: 3478575
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:35.806: Version: 10.1
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:35.806: Target: 1
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:35.806: Product: 65
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:35.806: sequence number is 1
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:35.806: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:35.806: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:5265): libfprint-device-DEBUG: 09:25:35.812: Device reported probe completion
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:35.812: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:5265): libfprint-device-DEBUG: 09:25:35.812: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(fprintd:5265): libfprint-device-DEBUG: 09:25:35.812: Not updating temperature model, device can run continuously!
(fprintd:5265): fprintd-DEBUG: 09:25:35.814: Device Synaptics Sensors scan type changed to 'press'
(fprintd:5265): fprintd-DEBUG: 09:25:35.814: Device Synaptics Sensors enroll stages changed to 9
(fprintd:5265): fprintd-DEBUG: 09:25:35.814: Finger present 0
(fprintd:5265): fprintd-DEBUG: 09:25:35.814: Finger needed 0
(fprintd:5265): fprintd-DEBUG: 09:25:35.815: entering main loop
(fprintd:5265): fprintd-DEBUG: 09:25:35.815: D-Bus service launched with name: net.reactivated.Fprint
(fprintd:5265): fprintd-DEBUG: 09:25:45.411: Requesting authorization from :1.140 to call method 'Claim' for device 'Synaptics Sensors'
(fprintd:5265): fprintd-DEBUG: 09:25:45.412: Getting authorization to perform Polkit action net.reactivated.fprint.device.verify
(fprintd:5265): fprintd-DEBUG: 09:25:45.423: Authorization granted to :1.140 to call method 'Claim' for device 'Synaptics Sensors'!
(fprintd:5265): fprintd-DEBUG: 09:25:45.424: user 'peter' claiming the device: 0
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:45.536: 1042982587: ../libfprint/libfprint/drivers/synaptics/synaptics.c:1391
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:45.536: sequence number is 2
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:45.536: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:5265): GLib-GIO-DEBUG: 09:25:45.537: GTask [gio] D-Bus interface method dispatch (source object: 0x56174bb9d350, source tag: 0x7f31d4445f50) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:45.537: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:5265): libfprint-device-DEBUG: 09:25:45.537: Device reported open completion
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:45.537: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:5265): libfprint-device-DEBUG: 09:25:45.537: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(fprintd:5265): libfprint-device-DEBUG: 09:25:45.537: Not updating temperature model, device can run continuously!
(fprintd:5265): fprintd-DEBUG: 09:25:45.537: claimed device 0
(fprintd:5265): fprintd-DEBUG: 09:25:45.538: Requesting authorization from :1.140 to call method 'EnrollStart' for device 'Synaptics Sensors'
(fprintd:5265): fprintd-DEBUG: 09:25:45.538: Getting authorization to perform Polkit action net.reactivated.fprint.device.enroll
(fprintd:5265): fprintd-DEBUG: 09:25:49.435: Authorization granted to :1.140 to call method 'EnrollStart' for device 'Synaptics Sensors'!
(fprintd:5265): fprintd-DEBUG: 09:25:49.435: file_storage_print_data_load(): loaded '/var/lib/fprint/peter/synaptics/1802d1957c26/7' Unbekannter Fehler -2
(fprintd:5265): fprintd-DEBUG: 09:25:49.435: start enrollment device 0 finger 7
(fprintd:5265): fprintd-DEBUG: 09:25:49.435: file_storage_discover_prints() for user 'admin' in '/var/lib/fprint/admin/synaptics/1802d1957c26'
(fprintd:5265): fprintd-DEBUG: 09:25:49.435: file_storage_print_data_load(): loaded '/var/lib/fprint/admin/synaptics/1802d1957c26/6' Erfolg
(fprintd:5265): fprintd-DEBUG: 09:25:49.435: file_storage_print_data_load(): loaded '/var/lib/fprint/admin/synaptics/1802d1957c26/9' Erfolg
(fprintd:5265): fprintd-DEBUG: 09:25:49.435: file_storage_discover_prints() for user 'admin' in '/var/lib/fprint/admin/synaptics/1802d1957c26'
(fprintd:5265): fprintd-DEBUG: 09:25:49.435: file_storage_print_data_load(): loaded '/var/lib/fprint/admin/synaptics/1802d1957c26/6' Erfolg
(fprintd:5265): fprintd-DEBUG: 09:25:49.435: file_storage_print_data_load(): loaded '/var/lib/fprint/admin/synaptics/1802d1957c26/9' Erfolg
(fprintd:5265): libfprint-device-DEBUG: 09:25:49.435: Not updating temperature model, device can run continuously!
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:49.435: data is 0x56174bb69290
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:49.435: 1046881545: ../libfprint/libfprint/drivers/synaptics/synaptics.c:851
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:49.435: sequence number is 3
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:49.435: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:5265): GLib-GIO-DEBUG: 09:25:49.435: GTask [gio] D-Bus interface method dispatch (source object: 0x56174bb9d350, source tag: 0x7f31d4445f50) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:49.435: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:49.449: data is 0x56174bb958c0
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:49.449: sequence number is 3
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:49.449: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:49.449: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:49.449: Place Finger on the Sensor!
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:49.449: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:52.948: interrupt transfer done
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:52.948: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:52.949: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:52.949: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:52.949: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:5265): libfprint-device-DEBUG: 09:25:52.949: Device reported finger status change: FP_FINGER_STATUS_PRESENT
(fprintd:5265): fprintd-DEBUG: 09:25:52.949: Finger present 1
(fprintd:5265): fprintd-DEBUG: 09:25:52.949: Finger needed 0
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:52.949: Finger is now on the sensor
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:52.949: Received message with 0 sequence number 0x91, ignoring!
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:52.949: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:53.060: interrupt transfer done
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.060: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.060: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.060: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.060: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.060: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:53.204: interrupt transfer done
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.204: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.205: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:53.205: Print is not in database
(fprintd:5265): libfprint-device-DEBUG: 09:25:53.205: Device reported identify completion
(fprintd:5265): libfprint-device-DEBUG: 09:25:53.205: Device reported finger status change: FP_FINGER_STATUS_NONE
(fprintd:5265): fprintd-DEBUG: 09:25:53.205: Finger present 0
(fprintd:5265): fprintd-DEBUG: 09:25:53.205: Finger needed 0
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.205: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:5265): libfprint-device-DEBUG: 09:25:53.205: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(fprintd:5265): libfprint-device-DEBUG: 09:25:53.205: Not updating temperature model, device can run continuously!
(fprintd:5265): libfprint-device-DEBUG: 09:25:53.206: Not updating temperature model, device can run continuously!
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:53.206: 1050651905: ../libfprint/libfprint/drivers/synaptics/synaptics.c:1002
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:53.206: user_id: FP1-20230724-7-7403AB89-peter, finger: 1
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:53.206: sequence number is 4
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.206: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.206: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:53.206: Enrollment has failed!: 213
(fprintd:5265): libfprint-device-DEBUG: 09:25:53.206: Device reported enroll completion
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.206: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:5265): libfprint-device-DEBUG: 09:25:53.206: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(fprintd:5265): libfprint-device-DEBUG: 09:25:53.206: Not updating temperature model, device can run continuously!
(fprintd:5265): fprintd-DEBUG: 09:25:53.206: enroll_cb: result enroll-unknown-error
(fprintd:5265): fprintd-WARNING **: 09:25:53.206: Device reported an error during enroll: Enrollment failed (213)
(fprintd:5265): fprintd-DEBUG: 09:25:53.207: Requesting authorization from :1.140 to call method 'EnrollStop' for device 'Synaptics Sensors'
(fprintd:5265): fprintd-DEBUG: 09:25:53.207: Authorization granted to :1.140 to call method 'EnrollStop' for device 'Synaptics Sensors'!
(fprintd:5265): GLib-GIO-DEBUG: 09:25:53.208: GTask [gio] D-Bus interface method dispatch (source object: 0x56174bb9d350, source tag: 0x7f31d4445f50) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:5265): fprintd-DEBUG: 09:25:53.208: Requesting authorization from :1.140 to call method 'Release' for device 'Synaptics Sensors'
(fprintd:5265): fprintd-DEBUG: 09:25:53.208: Authorization granted to :1.140 to call method 'Release' for device 'Synaptics Sensors'!
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:53.209: 1050654773: ../libfprint/libfprint/drivers/synaptics/synaptics.c:1412
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:53.209: sequence number is 5
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.209: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(fprintd:5265): GLib-GIO-DEBUG: 09:25:53.209: GTask [gio] D-Bus interface method dispatch (source object: 0x56174bb9d350, source tag: 0x7f31d4445f50) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.209: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(fprintd:5265): libfprint-synaptics-DEBUG: 09:25:53.209: Fingerprint sensor ready to be powered down
(fprintd:5265): libfprint-device-DEBUG: 09:25:53.209: Device reported close completion
(fprintd:5265): libfprint-SSM-DEBUG: 09:25:53.209: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(fprintd:5265): libfprint-device-DEBUG: 09:25:53.209: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(fprintd:5265): libfprint-device-DEBUG: 09:25:53.209: Not updating temperature model, device can run continuously!
(fprintd:5265): fprintd-DEBUG: 09:25:53.209: released device 0
```https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/160Ask for new device support Synaptic 06cb:009b2023-09-22T14:51:26ZLorenzo VeneriAsk for new device support Synaptic 06cb:009bHi, I'd like to use the synaptic fingerprint reader with 06cb:009b for a MSI laptop, Can you help me?Hi, I'd like to use the synaptic fingerprint reader with 06cb:009b for a MSI laptop, Can you help me?https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/161New version?2023-12-09T13:45:01ZTomasz KłoczkoNew version?https://gitlab.freedesktop.org/libfprint/fprintd/-/compare/v1.94.2...master shows ~20 commits since last release which was +year ago.
Is it possible to flush those commits as new minor release? :thinking:https://gitlab.freedesktop.org/libfprint/fprintd/-/compare/v1.94.2...master shows ~20 commits since last release which was +year ago.
Is it possible to flush those commits as new minor release? :thinking:https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/162ask support for Synaptic 04f3:0c5a2023-10-31T12:52:47ZGhost Userask support for Synaptic 04f3:0c5aHello,
It's would be nice to have support for 04f3:0c5a fingerprint sensor, it's the sensor for Microsoft Surface Laptop GoHello,
It's would be nice to have support for 04f3:0c5a fingerprint sensor, it's the sensor for Microsoft Surface Laptop Gohttps://gitlab.freedesktop.org/libfprint/fprintd/-/issues/165data: Fix typo in man pages2023-12-13T17:29:12ZIstván Donkódata: Fix typo in man pagesGitLab doesn't let me fork the repo for some reason, so I'm submitting this as an issue.
```patch
commit f0fdd2fe51ab36f83a5ba23087c948f7fddd31ea
Author: István Donkó <istvan.donko@gmail.com>
Date: Wed Dec 13 18:19:49 2023 +0100
...GitLab doesn't let me fork the repo for some reason, so I'm submitting this as an issue.
```patch
commit f0fdd2fe51ab36f83a5ba23087c948f7fddd31ea
Author: István Donkó <istvan.donko@gmail.com>
Date: Wed Dec 13 18:19:49 2023 +0100
data: Fix typo in man pages
diff --git a/data/fprintd.1 b/data/fprintd.1
index 0636df7..04574ee 100644
--- a/data/fprintd.1
+++ b/data/fprintd.1
@@ -142,11 +142,11 @@
fprintd \- Fingerprint management daemon, and test applications
.SH "SYNOPSIS"
.IX Header "SYNOPSIS"
-\&\fBfprintd-enroll\fR [\-f finger] [usename]
+\&\fBfprintd-enroll\fR [\-f finger] [username]
.PP
\&\fBfprintd-list\fR username [usernames...]
.PP
-\&\fBfprintd-verify\fR [\-f finger] [usename]
+\&\fBfprintd-verify\fR [\-f finger] [username]
.PP
\&\fBfprintd-delete\fR username [usernames...]
.SH "DESCRIPTION"
diff --git a/data/fprintd.pod b/data/fprintd.pod
index da8ab92..fe5fb80 100644
--- a/data/fprintd.pod
+++ b/data/fprintd.pod
@@ -4,11 +4,11 @@ fprintd - Fingerprint management daemon, and test applications
=head1 SYNOPSIS
-B<fprintd-enroll> [-f finger] [usename]
+B<fprintd-enroll> [-f finger] [username]
B<fprintd-list> username [usernames...]
-B<fprintd-verify> [-f finger] [usename]
+B<fprintd-verify> [-f finger] [username]
B<fprintd-delete> username [usernames...]
```
---
ps. If anyone knows what I might be doing wrong, please enlighten me! All I get is the following:
> _"An error occurred while forking the project. Please try again."_https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/166OpenCV update2024-01-07T12:40:29ZNikhil SinghOpenCV updateopenCV update `4.9.0-1` is not having `libopencv_features2d.so.408` in it, so fprintd service fails to start.
Using Arch linux with fprintd version `1.94.2-2`openCV update `4.9.0-1` is not having `libopencv_features2d.so.408` in it, so fprintd service fails to start.
Using Arch linux with fprintd version `1.94.2-2`https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/167Request to support device | 27c6:5f10 Shenzhen Goodix Technology Co.,Ltd. Goo...2024-01-17T12:22:35ZНикита ОбуховRequest to support device | 27c6:5f10 Shenzhen Goodix Technology Co.,Ltd. Goodix Fingerprint DeviceHello fprintd team!
I am using ALT Kworkstation 10.2.1 on Honor MagicBook X 16 Pro laptop.
I wanted to set up fingerprint login, but it turned out that device 04f3:0c4c is not supported.
Could you do me a favor and help me by adding sup...Hello fprintd team!
I am using ALT Kworkstation 10.2.1 on Honor MagicBook X 16 Pro laptop.
I wanted to set up fingerprint login, but it turned out that device 04f3:0c4c is not supported.
Could you do me a favor and help me by adding support for this device, please?https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/168Add support for Elan 04f3:0c702024-01-23T00:32:04ZKainoa KanterAdd support for Elan 04f3:0c70If you could add support for `ID 04f3:0c70 Elan Microelectronics Corp. ELAN:Fingerprint` found in the Redmibook Pro 15S (and possibly the ThinkBook 14-IML Laptop, although I'm not sure), that'd be great. I'd be happy to test or give any ...If you could add support for `ID 04f3:0c70 Elan Microelectronics Corp. ELAN:Fingerprint` found in the Redmibook Pro 15S (and possibly the ThinkBook 14-IML Laptop, although I'm not sure), that'd be great. I'd be happy to test or give any info that could help with development/debugging :)https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/169fprintd becomes unresponsive to sigterm when performing systemctl restart fpr...2024-01-25T20:41:50ZWheelerfprintd becomes unresponsive to sigterm when performing systemctl restart fprintdWhen I perform `systemctl restart fprintd`, `fprintd` does not respond to the `SIGTERM`:
```
$ sudo systemctl status fprintd
○ fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/usr/lib/systemd/system/fprintd.serv...When I perform `systemctl restart fprintd`, `fprintd` does not respond to the `SIGTERM`:
```
$ sudo systemctl status fprintd
○ fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: inactive (dead)
Docs: man:fprintd(1)
Jan 25 14:14:47 fedora systemd[1]: Stopping fprintd.service - Fingerprint Authentication Daemon...
Jan 25 14:15:32 fedora systemd[1]: fprintd.service: State 'stop-sigterm' timed out. Aborting.
Jan 25 14:15:32 fedora systemd[1]: fprintd.service: Killing process 313615 (fprintd) with signal SIGABRT.
Jan 25 14:15:32 fedora systemd[1]: fprintd.service: Main process exited, code=dumped, status=6/ABRT
Jan 25 14:15:32 fedora systemd[1]: fprintd.service: Failed with result 'timeout'.
Jan 25 14:15:32 fedora systemd[1]: Stopped fprintd.service - Fingerprint Authentication Daemon.
Jan 25 14:15:32 fedora systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Jan 25 14:15:33 fedora fprintd[348686]: Ignoring device due to initialization error: transfer timed out
Jan 25 14:15:33 fedora systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Jan 25 14:16:04 fedora systemd[1]: fprintd.service: Deactivated successfully.
```
This only happens when something wrong is going on with libfprint:
```
● fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: active (running) since Thu 2024-01-25 13:32:11 CST; 41min ago
Docs: man:fprintd(1)
Main PID: 313615 (fprintd)
Tasks: 7 (limit: 38096)
Memory: 1.7M
CPU: 82ms
CGroup: /system.slice/fprintd.service
└─313615 /usr/libexec/fprintd
Jan 25 13:32:11 fedora systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon...
Jan 25 13:32:11 fedora systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon.
Jan 25 13:43:15 fedora fprintd[313615]: Authorization denied to :1.1908 to call method 'Claim' for device 'Synaptics Sensors': Device was already claimed
Jan 25 13:56:47 fedora fprintd[313615]: Authorization denied to :1.1931 to call method 'Claim' for device 'Synaptics Sensors': Device was already claimed
Jan 25 13:58:10 fedora fprintd[313615]: Authorization denied to :1.1938 to call method 'Claim' for device 'Synaptics Sensors': Device was already claimed
Jan 25 14:03:33 fedora fprintd[313615]: Authorization denied to :1.1981 to call method 'Claim' for device 'Synaptics Sensors': Device was already claimed
Jan 25 14:13:52 fedora fprintd[313615]: Authorization denied to :1.2007 to call method 'Claim' for device 'Synaptics Sensors': Device was already claimed
Jan 25 14:14:03 fedora fprintd[313615]: Authorization denied to :1.2011 to call method 'Claim' for device 'Synaptics Sensors': Device was already claimed
```
But fprintd should respond to the sigterm regardless.
Is there a way to turn on some debug logging so I can provide some more useful logs?https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/170Existing fingerprint will disappear when add new fingerprint.2024-02-26T08:18:17ZJulius EndrinaExisting fingerprint will disappear when add new fingerprint.The existing enrolled fingerprint will disapper after adding a new fingerprint. Add the same fingerprint but then cancel before it is completed.
System: Lenovo ThinkPad P14s
OS: Fedora 39
Kernel: 6.6.13-200.fc39.x86_64
Libfprint version...The existing enrolled fingerprint will disapper after adding a new fingerprint. Add the same fingerprint but then cancel before it is completed.
System: Lenovo ThinkPad P14s
OS: Fedora 39
Kernel: 6.6.13-200.fc39.x86_64
Libfprint version: 1.94.6
FPR: Goodix MOC (product id: 6594)
**Steps to reproduce:**
1. Install Fedora 39.
2. Update libfprint to 1.94.6.
3. Reboot the system.
4. Open settings, users.
5. Enroll the right index finger.
6. Closed the setting, users screen.
7. Lock/unlock screen using the enrolled fingerprint.
8. Open settings, users.
9. Add new fingerprint. Enroll the same right index finger previously enrolled.
10. Don't complete the enrollment process, click cancel.
11. Check the settings, user screen. The previously enrolled fingerprint is gone.
**[Expected Result]**
Original fingerprint will not disappear. Or cannot re-enroll an enrolled fingerprint.
**[Actual result]**
The original fingerprint will disappear after cancelling the re-enrollment of the same fingerprint.
**[Logs]**
journalctl: [journal_fpr.log](/uploads/e0d569d110005350191f5a873dce93bd/journal_fpr.log)
dmesg:[dmesg_fpr.log](/uploads/89c59538ef08af082fcc9769dde953f5/dmesg_fpr.log)
libfprint:[libfprint_info.log](/uploads/5f61915a9676b3657b827cb21033a691/libfprint_info.log)https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/171Some finger missing after enrollment.2024-03-08T05:31:52ZJulius EndrinaSome finger missing after enrollment.The newly enrolled fingerprints could still be found on the drop down list after the enrollment while some fingerprints that was not enrolled disappeared.
System: Lenovo ThinkPad P14s
OS: Fedora 40 (can be reproduced also on Fedora 39)...The newly enrolled fingerprints could still be found on the drop down list after the enrollment while some fingerprints that was not enrolled disappeared.
System: Lenovo ThinkPad P14s
OS: Fedora 40 (can be reproduced also on Fedora 39)
Kernel: 6.8.0-0.rc6.49fc40.x86_64
Libfprint version: 1.94.6
Fprintd version: 1.94.2
FPR: Goodix MOC (product id: 6594)
**Steps to reproduce:**
1. Install Fedora 39 or 40.
2. Open settings --> System --> Users
3. Enroll the right index finger.
4. Enroll the right middle finger.
5. Click scan new fingerprint and observe the dropdown list.
**Expected Result:** The right index finger and right middle finger should not be in the dropdown list.
**Actual result:** The left little finger and left thumb finger disappeared from the dropdown list. The right index finger and right middle finger is still in the dropdown list.
**Screenshots:**
Before enrollment- ![before_enrollment](/uploads/0ccf45fdc5ddf6af1197ac85c69a8690/before_enrollment.png)
After enrollment- ![afer_enrollment](/uploads/4dd9554e55e82cfbdac250febefc4996/afer_enrollment.png)
**Logs:**
journalctl- [journal.log](/uploads/2ce8e0a81fa467fe823f9e19d8922dd4/journal.log)
dmesg- [dmesg.log](/uploads/5f1e4349288fe4e71e4bd42c0def9a0a/dmesg.log)