Support Synaptics fingerprint device with ID [06CB:0106]

[Leo Lin]

The ID [06CB:0106] is included in https://salsa.debian.org/debian/libfprint/-/commit/427139f347c576e08d6656142ba39d06c7be2b15

[Impact]

 * Support Synaptics [06CB:0106] fingerprint component.

[Test Plan]

 * Find a machine with this fingerprint device

 * Launch `settings` and enable `Fingerprint Login`

 * Enroll finger and then logout

 * Login system with enrolled finger

[Where problems could occur]

 * If the vendor uses the same ID for other devices, the new device may not work properly.

[Leo Lin (0xff07)]

Salsa MP: https://salsa.debian.org/ubuntu-dev-team/libfprint/-/merge_requests/14

[Timo Aaltonen (tjaalton)]

Hello Leo, or anyone else affected,

Accepted libfprint into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libfprint/1:1.94.3+tod1-0ubuntu2~22.04.07 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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

[Timo Aaltonen (tjaalton)]

please upload to noble before release

[Leo Lin (0xff07)]

Tested on the machines with the said fingerprint hardware using the following procedures:

1. Enable the -proposed channel
2. Install 1:1.94.3+tod1-0ubuntu2~22.04.07 version of libfprint-2-2, which is the one in the -proposed channel
3. Reboot the machine
4. After the reboot, confirm that fingerprint login option appears in the user tab of the setting menu
5. Confirm that fingerprint could be registered.
6. Log out from the user, and confirm that it could be logged in with the registered fingerprint

[Andreas Hasenack (ahasenack)]

I see it in noble[1], but not mantic[2], and there is no mention in this bug about skipping mantic on purpose. When interim releases are skipped, it's best to explicitly declare the intent and reason.

1. https://git.launchpad.net/ubuntu/+source/libfprint/tree/libfprint/drivers/synaptics/synaptics.c?h=applied/ubuntu/devel#n50
2. https://git.launchpad.net/ubuntu/+source/libfprint/tree/libfprint/drivers/synaptics/synaptics.c?h=applied/ubuntu/mantic-devel#n33

[Sebastien Bacher (seb128)]

@Andreas, The main reason is that the fix is for oem hardware enablement and those target LTS series.

[Leo Lin (0xff07)]

My bad not realizing that non-LTS versions are not maintained on salsa. This is the debdiff for mantic.