libfprint issueshttps://gitlab.freedesktop.org/groups/libfprint/-/issues2021-02-05T18:00:26Zhttps://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/libfprint/-/issues/94Possible large mem alloc in lfs_detect_minutiae_V2()2018-11-29T11:38:00ZBastien NoceraPossible large mem alloc in lfs_detect_minutiae_V2()From https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1745454/comments/2
> - lfs_detect_minutiae_V2() memory allocation with iw*ih, no input bounds
> visibleFrom https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1745454/comments/2
> - lfs_detect_minutiae_V2() memory allocation with iw*ih, no input bounds
> visible1.0https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/93Use memcpy or memmove in morph_TF_map()2018-11-29T11:38:13ZBastien NoceraUse memcpy or memmove in morph_TF_map()From https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1745454/comments/2
> - morph_TF_map() -- should those loops be replaced with memcpy() or
> memmove()?From https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1745454/comments/2
> - morph_TF_map() -- should those loops be replaced with memcpy() or
> memmove()?2.0https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/84sanitize_image() doesn't check dimensions2018-11-29T11:39:35ZSeth Arnoldsanitize_image() doesn't check dimensions`sanitize_image()` does not validate reasonable height and width
parameters.
(It's also only called from one function; perhaps this is sufficient,
but I expected to see it more often.)
Thanks`sanitize_image()` does not validate reasonable height and width
parameters.
(It's also only called from one function; perhaps this is sufficient,
but I expected to see it more often.)
Thanks1.0https://gitlab.freedesktop.org/libfprint/wiki/-/issues/102Please add support for microarray Inc. fingerprint sensor2024-03-28T10:03:26Z王 毅Please add support for microarray Inc. fingerprint sensorzlxgzlx-vm:~Libfprint-microarry$ 1susb vd 3274:8012
Bus 001 Device 007: ID 3274:B012 MicroarrayTechnology MAFP General Device
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDes...zlxgzlx-vm:~Libfprint-microarry$ 1susb vd 3274:8012
Bus 001 Device 007: ID 3274:B012 MicroarrayTechnology MAFP General Device
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x3274
idProduct 0x8012
bcdDevice 1.00
iManufacturer 1 MicroarrayTechnology
iProduct 2 MAFP General Device
iSerial 3 1120031604020321
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0027
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1https://gitlab.freedesktop.org/libfprint/wiki/-/issues/101No support for ID: 138a:003f (Validity Sensors, Inc. - VFS495 Fingerprint Rea...2024-03-25T18:23:01ZEric DavantureNo support for ID: 138a:003f (Validity Sensors, Inc. - VFS495 Fingerprint Reader) on HP ZBook 17 G3Title says it all: fprint is not supporting sensor: ID: 138a:003f (Validity Sensors, Inc. - VFS495 Fingerprint Reader) on HP ZBook 17 G3
Thanks.Title says it all: fprint is not supporting sensor: ID: 138a:003f (Validity Sensors, Inc. - VFS495 Fingerprint Reader) on HP ZBook 17 G3
Thanks.https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/6102541:0236 Chipsailing CS9711Fingprint2024-03-21T10:04:32ZFreerk Jongsma2541:0236 Chipsailing CS9711FingprintBought a nice usb fingerprint scanner.
It works on Windows
I get this error message:
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No
devices availableBought a nice usb fingerprint scanner.
It works on Windows
I get this error message:
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No
devices availablehttps://gitlab.freedesktop.org/libfprint/libfprint/-/issues/609re-asking for support for `06cb:00be` Synaptics2024-03-17T16:51:07ZHannez Kannezre-asking for support for `06cb:00be` SynapticsI know that there are two 3 year old issues about this model(#328 and #296), but was there an effort to get sit to work? Unfortunately I have nowhere near the skills needed to do this.
Question is if I should hope for this to work some d...I know that there are two 3 year old issues about this model(#328 and #296), but was there an effort to get sit to work? Unfortunately I have nowhere near the skills needed to do this.
Question is if I should hope for this to work some day at all or not?https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/608goodixmoc: Add PID 0x609A2024-03-16T10:49:25ZLee Jiajunwlmqljj@qq.comgoodixmoc: Add PID 0x609AI can confirm that the device "27c6:609a Shenzhen Goodix Technology Co., Ltd. Goodix USB2.0 MISC" can run with the existing driver.
PR: libfprint/libfprint!471
My laptop: Mechrevo Wujie 14 pro-7840HS
[inxi.txt](/uploads/ed7ab76d32aad6...I can confirm that the device "27c6:609a Shenzhen Goodix Technology Co., Ltd. Goodix USB2.0 MISC" can run with the existing driver.
PR: libfprint/libfprint!471
My laptop: Mechrevo Wujie 14 pro-7840HS
[inxi.txt](/uploads/ed7ab76d32aad62e1af793f15a2fbdad/inxi.txt)
[0001-goodixmoc-Add-PID-0x609A.patch](/uploads/2d674e388a268b79ccd2ce26d719f7b0/0001-goodixmoc-Add-PID-0x609A.patch)
[fprint_log.txt](/uploads/b1229a21a92462db53c9ca523f43dedb/fprint_log.txt)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)https://gitlab.freedesktop.org/libfprint/wiki/-/issues/10010a5:a120 FPC Sensor controller support2024-03-07T10:43:05ZTakeshi10a5:a120 FPC Sensor controller supportPlease add support for FPC sensor controller 10a5:a120
uname -r
`6.7.8-zen1-1-zen`
sudo lsusb -vd 10a5:a120
```
Bus 001 Device 014: ID 10a5:a120 FPC FPC Sensor Controller
Device Descriptor:
bLength 18
bDescriptorType ...Please add support for FPC sensor controller 10a5:a120
uname -r
`6.7.8-zen1-1-zen`
sudo lsusb -vd 10a5:a120
```
Bus 001 Device 014: ID 10a5:a120 FPC FPC Sensor Controller
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 [unknown]
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x10a5 FPC
idProduct 0xa120 FPC Sensor Controller
bcdDevice 0.72
iManufacturer 1 FPC
iProduct 2 FPC Sensor Controller
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4 FPC Sensor Controller
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 5 FPC Sensor Controller L:0001 FW:12.26.0.72
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0002
(Bus Powered)
Remote Wakeup Enabled
```
windows driver :[Fingerprint_FPC_12.26.0.72.zip](/uploads/4afb2fa143dcae21eb5e7deacad44d90/Fingerprint_FPC_12.26.0.72.zip)https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/6071c7a:0587 Egis Technology Inc. (aka. LighTuning) partial support (egismoc)2024-03-05T05:59:28ZTamer Hassan1c7a:0587 Egis Technology Inc. (aka. LighTuning) partial support (egismoc)Hi,
I'm a developer but clueless as to where to begin.
I have an Asus Creator Q laptop (Product name: Vivobook_ASUSLaptop K6502VJ_Q540VJ)
After some tinkering with libfprint, I got some action-response from the fp sensor with fprintd-enr...Hi,
I'm a developer but clueless as to where to begin.
I have an Asus Creator Q laptop (Product name: Vivobook_ASUSLaptop K6502VJ_Q540VJ)
After some tinkering with libfprint, I got some action-response from the fp sensor with fprintd-enroll
```
$ lsusb | grep LighTuning
Bus 003 Device 002: ID 1c7a:0587 LighTuning Technology Inc. ETU905A88-E
```
What I did:
in `libfprint/drivers/egismoc/egismoc.c` , after lines 52-53:
```
static const FpIdEntry egismoc_id_table[] = {
{ .vid = 0x1c7a, .pid = 0x0582, .driver_data = EGISMOC_DRIVER_CHECK_PREFIX_TYPE1 },
```
I added:
```
{ .vid = 0x1c7a, .pid = 0x0587, .driver_data = EGISMOC_DRIVER_CHECK_PREFIX_TYPE1 },
```
and in `data/autosuspend.hwdb` , after lines 80-81:
```
# Supported by libfprint driver egismoc
usb:v1C7Ap0582*
```
I added:
```
usb:v1C7Ap0587*
```
After building and installing, I was able to get the following action-response behavior:
```
t@creator:~/libfprint-1.94.7+tod1$ sudo fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-remove-and-retry
Enroll result: enroll-remove-and-retry
Enroll result: enroll-remove-and-retry
Enroll result: enroll-remove-and-retry
^C
```
Each line "Enroll result:" was triggered by a index finger touch on the fingerprint sensor.
The same "Enroll result:" sequence (first one "enroll-stage-passed" followed by infinite "enroll-remove-and-retry" to each additional touch) is replicated when setting `.driver_data = EGISMOC_DRIVER_CHECK_PREFIX_TYPE2` instead of TYPE1 in `libfprint/drivers/egismoc/egismoc.c`.
Is adding support possible?
Where to start?
I can possibly contribute!
P.S. Is windows driver of any help or even need? (reverse-engineering?)
https://dlcdnets.asus.com/pub/ASUS/nb/Image/Driver/BiometricAuthentication/31789/Fingerprint_WBF_USB_DCH_EGIS_F_V1.1.38.0_31789.exe?model=Q540VJ
Cheershttps://gitlab.freedesktop.org/libfprint/libfprint/-/issues/606Unable to enroll fingerprint on Samusng Galaxy Book 3 pro2024-03-01T18:04:29ZHugo KirchUnable to enroll fingerprint on Samusng Galaxy Book 3 proHello.
I am experiencing some trouble trying to enroll my fingerprint on my laptop.
Here is what happens when i try to enroll a fingerprint :
> fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-i...Hello.
I am experiencing some trouble trying to enroll my fingerprint on my laptop.
Here is what happens when i try to enroll a fingerprint :
> fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
*asks for password*
Enroll result: enroll-stage-passed <- but i didn't touch the reader
Enroll result: enroll-unknown-error <- once i touch the reader
Result of lsusb -v concerning the reader :
```
Bus 003 Device 002: ID 1c7a:05a1 LighTuning Technology Inc. ETU905A80-E
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1c7a LighTuning Technology Inc.
idProduct 0x05a1 ETU905A80-E
bcdDevice 12.07
iManufacturer 1 EGIS
iProduct 2 ETU905A80-E
iSerial 3 0B5C3BPKB254
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0027
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0 [unknown]
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 5
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 [unknown]
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered
```
I'm runing Archlinux with currently kernel 6.7.6.arch1-2
libfprint version is 1.94.7-1
fprintd version is 1.94.2-2
Can anyone help me with this ?
Thankshttps://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/wiki/-/issues/99Add 04f3:0c7c Elan Microelectronics to supported devices2024-02-24T06:54:53ZPavel KolskýAdd 04f3:0c7c Elan Microelectronics to supported devicesAfter following [these steps](https://gitlab.freedesktop.org/depau/libfprint/-/issues/6), I got my fingerprint reader working on my Acer TravelMate Spin P614RN-52. Without this patch, the reader was not working. Is there a way to apply i...After following [these steps](https://gitlab.freedesktop.org/depau/libfprint/-/issues/6), I got my fingerprint reader working on my Acer TravelMate Spin P614RN-52. Without this patch, the reader was not working. Is there a way to apply it to the main branch?
Thankshttps://gitlab.freedesktop.org/libfprint/libfprint/-/issues/6042808:c652 HOLTEK FocalTech Fingerprint Device | Tecno Megabook T1 | Unsup...2024-02-21T20:28:29ZAmpernic2808:c652 HOLTEK FocalTech Fingerprint Device | Tecno Megabook T1 | UnsupportedPlease, add support of this FocalTech fp usb scaner. I can provide any needed information about hardware and any test of builds.
Base information:
**$lsb_release -a**
```
No LSB modules are available.
Distributor ID: Ubuntu
Description...Please, add support of this FocalTech fp usb scaner. I can provide any needed information about hardware and any test of builds.
Base information:
**$lsb_release -a**
```
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
```
**$ uname -r**
```
6.5.0-17-generic
```
**$ sudo lsusb -vd 2808:c652**
```
Bus 001 Device 002: ID 2808:c652 HOLTEK FocalTech Fingerprint Device
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 2
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2808
idProduct 0xc652
bcdDevice 2.03
iManufacturer 1 HOLTEK
iProduct 2 FocalTech Fingerprint Device
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)
```
**Windows driver:**
[ftwbiodriverumdfv3.inf_amd64_1bd8fb1f80da33c7.zip](/uploads/178c9fc49f88e647b02707d6fed206f3/ftwbiodriverumdfv3.inf_amd64_1bd8fb1f80da33c7.zip)
In the ".ini" file for driver installation the same compatible in "focaltech_moc.c" pid "a959" is specified, but when adding the required "c652" to it I get libusb error when executing examples/enroll:
```
(process:11077): libfprint-focaltech_moc-DEBUG: 20:03:52.122: 2568081098: ../libfprint/drivers/focaltech_moc/focaltech_moc.c:1850
(process:11077): libfprint-device-WARNING **: 20:03:52.123: Failed to disable USB persist by writing to /sys/bus/usb/devices/1-3/power/persist
(process:11077): libfprint-device-DEBUG: 20:03:52.123: Device reported probe completion
(process:11077): libfprint-device-DEBUG: 20:03:52.123: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:11077): libfprint-device-DEBUG: 20:03:52.123: Not updating temperature model, device can run continuously!
Selected device 0 (Focaltech MOC Sensors) claimed by focaltech_moc driver
(process:11077): libfprint-focaltech_moc-DEBUG: 20:03:52.409: class:a, subclass:0, protocol:0
(process:11077): libfprint-focaltech_moc-DEBUG: 20:03:52.409: bytes size:0
(process:11077): libfprint-focaltech_moc-DEBUG: 20:03:52.409: kind:5, max packet size:64, poll interval:0, refresh:0, sync address:0, address:3, number:3, direction:G_USB_DEVICE_DIRECTION_HOST_TO_DEVICE
(process:11077): libfprint-focaltech_moc-DEBUG: 20:03:52.409: bytes size:0
(process:11077): libfprint-focaltech_moc-DEBUG: 20:03:52.409: kind:5, max packet size:64, poll interval:0, refresh:0, sync address:0, address:81, number:1, direction:G_USB_DEVICE_DIRECTION_DEVICE_TO_HOST
(process:11077): libfprint-SSM-DEBUG: 20:03:52.409: [focaltech_moc] DEV_INIT_STATES entering state 0
(process:11077): libfprint-SSM-DEBUG: 20:03:52.409: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
(process:11077): libfprint-SSM-DEBUG: 20:03:52.409: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
libusb: error [udev_hotplug_event] ignoring udev action change
libusb: error [udev_hotplug_event] ignoring udev action change
```
And process stuck.
**Part of ACPI dump in windows:**
(Maybe it can be helpful)
Full device ACPI path - \_SB.PCI0.GP17.XHC0.RHUB.PRT3
```
/* Some roots */
Device ()
{
Name (_ADR, 0x03) // _ADR: Address
Name (UPC1, Package (0x04)
{
Zero,
0xFF,
Zero,
Zero
})
Method (_UPC, 0, Serialized) // _UPC: USB Port Capabilities
{
Return (UPC1) /* \_SB_.PCI0.GP17.XHC0.RHUB.PRT3.UPC1 */
}
Name (PLD1, Package (0x01)
{
Buffer (0x14)
{
/* 0000 */ 0x82, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0008 */ 0x58, 0x1C, 0x80, 0x01, 0x01, 0x00, 0x00, 0x00, // X.......
/* 0010 */ 0xFF, 0xFF, 0xFF, 0xFF // ....
}
})
Method (_PLD, 0, Serialized) // _PLD: Physical Location of Device
{
Return (PLD1) /* \_SB_.PCI0.GP17.XHC0.RHUB.PRT3.PLD1 */
}
}
/* Another device */
Device (PRT3)
{
Name (_ADR, 0x03) // _ADR: Address
Name (UPC1, Package (0x04)
{
0xFF,
0x03,
Zero,
Zero
})
Method (_UPC, 0, Serialized) // _UPC: USB Port Capabilities
{
Return (UPC1) /* \_SB_.PCI0.GP17.XHC1.RHUB.PRT3.UPC1 */
}
Name (PLD1, Package (0x01)
{
Buffer (0x14)
{
/* 0000 */ 0x82, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, // ........
/* 0008 */ 0x91, 0x1C, 0x80, 0x03, 0x01, 0x00, 0x00, 0x00, // ........
/* 0010 */ 0xFF, 0xFF, 0xFF, 0xFF // ....
}
})
Method (_PLD, 0, Serialized) // _PLD: Physical Location of Device
{
Return (PLD1) /* \_SB_.PCI0.GP17.XHC1.RHUB.PRT3.PLD1 */
}
Method (_RMV, 0, NotSerialized) // _RMV: Removal Status
{
If ((THPN == 0x04))
{
Return (Zero)
}
Else
{
Return (One)
}
}
}
```https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/603Question about minutiae file format changes in the future2024-02-22T07:25:10ZZoltán BöszörményiQuestion about minutiae file format changes in the futureMy company started using libprint+fprintd for biometric authentication a few of years ago, to replace a proprietary fingerprint reader SDK, at the time with libfprint 1.0 / fprintd 0.9.
Now, we plan to upgrade to the 1.9x beta version a...My company started using libprint+fprintd for biometric authentication a few of years ago, to replace a proprietary fingerprint reader SDK, at the time with libfprint 1.0 / fprintd 0.9.
Now, we plan to upgrade to the 1.9x beta version and the minutiae file format changed, so re-enrolling fingerprints is necessary again.
My question is: are there any plans to change the minutiae format between 1.94.7 and the final 2.0?
Thanks in advance.https://gitlab.freedesktop.org/libfprint/wiki/-/issues/982808:c652 HOLTEK FocalTech Fingerprint Device | Tecno Megabook T1 | Unsup...2024-02-20T22:43:17ZAmpernic2808:c652 HOLTEK FocalTech Fingerprint Device | Tecno Megabook T1 | UnsupportedPlease, add support of this FocalTech fp usb scaner. I can provide any needed information about hardware and any test of builds.
Base information:
**$lsb_release -a**
```
No LSB modules are available.
Distributor ID: Ubuntu
Description...Please, add support of this FocalTech fp usb scaner. I can provide any needed information about hardware and any test of builds.
Base information:
**$lsb_release -a**
```
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
```
**$ uname -r**
```
6.5.0-17-generic
```
**$ sudo lsusb -vd 2808:c652**
```
Bus 001 Device 002: ID 2808:c652 HOLTEK FocalTech Fingerprint Device
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 2
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2808
idProduct 0xc652
bcdDevice 2.03
iManufacturer 1 HOLTEK
iProduct 2 FocalTech Fingerprint Device
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)
```
**Windows drivers:**
[ftwbiodriverumdfv3.inf_amd64_1bd8fb1f80da33c7.zip](/uploads/178c9fc49f88e647b02707d6fed206f3/ftwbiodriverumdfv3.inf_amd64_1bd8fb1f80da33c7.zip)https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/602Add support for 138a:0097 Validity Sensors. (Thinkpad T470s)2024-03-08T12:37:48ZAntti SavolainenAdd support for 138a:0097 Validity Sensors. (Thinkpad T470s)This was previously discussed about 5-3 years ago. https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/123
In the discussion there were two repositories that seemed to have achieved functional drivers, one by @jeffgoh
https://g...This was previously discussed about 5-3 years ago. https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/123
In the discussion there were two repositories that seemed to have achieved functional drivers, one by @jeffgoh
https://github.com/jeffgoh/libfprint
https://github.com/hrenod/libfprint
Would it be possible to go through these repositories to achieve functionality?https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/601[04f3:0c11] cannot enroll--ignores all touches after the first or second one2024-02-19T09:03:59ZM1N3R[04f3:0c11] cannot enroll--ignores all touches after the first or second oneThis is a crosspost from [wiki issue 92](https://gitlab.freedesktop.org/libfprint/wiki/-/issues/92), in the hopes of getting it in front of the right people after total radio silence on the original issue for over three, going on four mo...This is a crosspost from [wiki issue 92](https://gitlab.freedesktop.org/libfprint/wiki/-/issues/92), in the hopes of getting it in front of the right people after total radio silence on the original issue for over three, going on four months AOW.
While all the details are already in the original issue, I may as well rehash them here, with some minor updates from my current situation:
My laptop has an ELAN trackpad with an embedded fingerprint sensor (vendor/product ID `04f3:0c11`) that was supported natively in Windows and worked perfectly until I switched to Kubuntu, then Pop!_OS 4 months and change ago.
When I try to enroll a fingerprint, whether graphically within GNOME Settings, or using fprintd-enroll, I can swipe my finger down the sensor for an `enroll-stage-passed` only once, and very rarely twice, before it completely stops responding to any further swiping, poking, or prodding until it gives up, spitting out an `enroll-unknown-error`. This happens every single time I try to enroll a finger, and it is **maddening**, to the point that I'm seriously considering distro-hopping to Arch (or another rolling release distro) so I can get my hands on an official fix that much quicker.
If you need any further information from me, please do not hesitate to let me know. I check my email with some semblance of regularity, so you'll hear back from me as soon as I have time to spare.
Thanks for listening to me ramble. I have also attached a video of me demonstrating the issue in case that may help: ![2024-02-16_22-10-22](/uploads/411be59dead46c041dcbe3647df47b25/2024-02-16_22-10-22.mp4)