Request for adding support for Synaptics fingerprint reader sensors: 0xE9 and 0xDF

[Chih-Hsyuan Ho]

[Impact]

 * We were advised by Synaptics to upgrade the existing libfprint in the archive to include sensor support for 0xE9 and 0xDF as highlighted in the following commits:

https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/8b64312f4bfee84c8be1eb9763f7fe87ec078a1a

[Test Case]

 * We have several OEM platforms with these Synaptics sensors enabled with Focal and they can be used to validate these changes.

[Regression Potential]

 * Regression potential for an updated libfprint with these new PIDs is low

[Other Info]

 None

[Launchpad Janitor (janitor)]

This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu1

---------------
libfprint (1:1.90.3+tod1-0ubuntu1) groovy; urgency=medium

  * New upstream release (LP: #1896861):
    - New goodixmoc driver supporting Goodix USB devices:
      27C6:5840, 27C6:6496, 27C6:60A2
    - Newly added support for Synaptics device:
      06CB:00E9 06CB:00DF (LP: #1893719)
    - Fixed an issue with Synaptics devices sometimes not working at boot
      (LP: #1893719)
    - Fix issue with aes3k driver
  * debian/libfprint-2-tod1.symbols: Added new GType symbols

 -- Marco Trevisan (Treviño) <email address hidden> Thu, 24 Sep 2020 06:14:30 +0200

[Timo Aaltonen (tjaalton)]

Hello Chih-Hsyuan, or anyone else affected,

Accepted libfprint into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libfprint/1:1.90.2+tod1-0ubuntu1~20.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Chih-Hsyuan Ho (chih)]

Downloaded and checked the libfprint source in 1:1.90.2+tod1-0ubuntu1~20.04.2 in proposed, and 0xE9 and 0xDF had indeed been added to lifprint/drivers/synaptics/synaptics.c

[Launchpad Janitor (janitor)]

This bug was fixed in the package libfprint - 1:1.90.2+tod1-0ubuntu1~20.04.2

---------------
libfprint (1:1.90.2+tod1-0ubuntu1~20.04.2) focal; urgency=medium

  * d/p/synaptics-retry-get-version-command-once-when-receiving-n.patch,
    d/p/synaptics-support-sensors-pid-0xe9-0xdf.patch:
    - Newly added support for Synaptics devices 06CB:00E9 06CB:00D
      (LP: #1893719)

 -- Marco Trevisan (Treviño) <email address hidden> Thu, 24 Sep 2020 06:38:08 +0200

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for libfprint has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[zhang, chun-guang (clevo0507)]

Hi Team

I'm not familiar with ubuntu.
I got similar issue on HP elitebook G7 notebook fingerprint want to fix this issue:
could you pls advice how to install below package?
I means how to run command?

https://launchpad.net/ubuntu/+source/libfprint/1:1.90.2+tod1-0ubuntu1~20.04.2
Downloads
File Size SHA-256 Checksum
libfprint_1.90.2+tod1.orig.tar.xz
libfprint_1.90.2+tod1-0ubuntu1~20.04.2.debian.tar.xz
libfprint_1.90.2+tod1-0ubuntu1~20.04.2.dsc

Thanks

BR
Terry

[Gabor Enyedi (enyecz)]

Hi!

Since version 1.90.7, the support of this device has gone. I tried to use the old version with no success (old version drops "(process:124322): libfprint-synaptics-DEBUG: 15:34:15.238: Enrollment has failed!: 104", new version says the device is not supported). It would be nice to have support.
I have a HP G8 Elitebook x360 1040.
BR,

Gabor

[Andy Chi (andch)]

Hi,
Can you help to upload lsusb to us?

Here is the synaptics IDs are supported in the latest libfprint 1:1.90.2+tod1-0ubuntu1~20.04.6

  { .vid = SYNAPTICS_VENDOR_ID, .pid = 0xBD, },
  { .vid = SYNAPTICS_VENDOR_ID, .pid = 0xE9, },
  { .vid = SYNAPTICS_VENDOR_ID, .pid = 0xDF, },
  { .vid = SYNAPTICS_VENDOR_ID, .pid = 0xF9, },
  { .vid = SYNAPTICS_VENDOR_ID, .pid = 0xFC, },
  { .vid = SYNAPTICS_VENDOR_ID, .pid = 0xC2, },
  { .vid = SYNAPTICS_VENDOR_ID, .pid = 0xC9, },
  { .vid = SYNAPTICS_VENDOR_ID, .pid = 0xE7, },

[Andy Chi (andch)]

BTW can you try the libfprint here?
https://launchpad.net/~andch/+archive/ubuntu/staging-fprint
the version is 1:1.90.2+tod1-0ubuntu1~20.04.7~1. This version is now in SRU process.

[Gabor Enyedi (enyecz)]

Hi!

The situation is this: This thing got support in 1.90.2 and lost support in 1.92.0. I tried multiple different versions with the very same result: the "supported" versions all fail with all the firmwares I found, including the latest one, which has a note that "Linux support added". :) The reason seems that the driver and the device do not follow the same protocol. From 1.92.0 to 1.94.3, this device is put to a non-supported known device list (I guess, because it was recognized to be bad).
I tried the version from staging, as you asked, the situation is the same as with all the others.
I don't really know how to test this thing beyond that checking the service (fprint.service) is running and checking if there is an option for fingerprint at gnome-control-center. My best guess is the "enroll" example, which I got when I compiled a version from source. When I use "enroll", I got the "best" result with the latest firmware and a version below 1.92.0. This is as follows (with 1.90.7, but this is the same for all):

boe@x71487tl:~/src/libfprint/build/examples$ sudo ./enroll
[sudo] password for boe:
This program will enroll the selected finger, unconditionally overwriting any print for the same finger that was enrolled previously. If you want to continue, press enter, otherwise hit Ctrl+C

Choose the finger to enroll:
  [0] left thumb
  [1] left index
  [2] left middle
  [3] left ring
  [4] left little
  [5] right thumb
  [6] right index
  [7] right middle
  [8] right ring
  [9] right little
> 6
(process:148955): libfprint-context-DEBUG: 17:09:21.343: No driver found for USB device 1D6B:0003
(process:148955): libfprint-synaptics-DEBUG: 17:09:21.344: 29579161481: ../libfprint/drivers/synaptics/synaptics.c:902
(process:148955): libfprint-synaptics-DEBUG: 17:09:21.624: Build Time: 1596608839
(process:148955): libfprint-synaptics-DEBUG: 17:09:21.624: Build Num: 3273255
(process:148955): libfprint-synaptics-DEBUG: 17:09:21.624: Version: 10.1
(process:148955): libfprint-synaptics-DEBUG: 17:09:21.624: Target: 1
(process:148955): libfprint-synaptics-DEBUG: 17:09:21.624: Product: 65
(process:148955): libfprint-device-DEBUG: 17:09:21.624: Device reported probe completion
(process:148955): libfprint-context-DEBUG: 17:09:21.625: No driver found for USB device 0408:5349
(process:148955): libfprint-context-DEBUG: 17:09:21.625: No driver found for USB device 8087:0026
(process:148955): libfprint-context-DEBUG: 17:09:21.625: No driver found for USB device 1D6B:0002
(process:148955): libfprint-context-DEBUG: 17:09:21.625: No driver found for USB device 1D6B:0003
(process:148955): libfprint-context-DEBUG: 17:09:21.625: No driver found for USB device 1D6B:0002
(process:148955): libfprint-device-DEBUG: 17:09:21.625: Completing action FPI_DEVICE_ACTION_PROBE in idle!
Selected device b721527cc3a2 (Synaptics Sensors) claimed by synaptics driver
(process:148955): libfprint-synaptics-DEBUG: 17:09:21.625: 29579442647: ../libfprint/drivers/synaptics/synaptics.c:1079
libusb: error [udev_hotplug_event] ignoring udev action change
(process:148955): libfprint-synaptics-DEBUG: 17:09:21.899: sequence number is 1
(process:148955): libfprint-SSM-DEBUG: 17:09:21.899: [synaptics...