[needs-packaging] libfprint-2-tod1-goodix

the package was built by a test ppa:

https://launchpad.net/~alextu/+archive/ubuntu/test3/+packages?field.name_filter=goodix&field.status_filter=published&field.series_filter=

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for a new package in Ubuntu. As a part of the managing needs-packaging bug reports specification, https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-packaging bug reports have Wishlist importance. Subsequently, I'm setting this bug's status to Wishlist.

Thank you for your work, I had a look to what is in the ppa and I've a question

the source and deb only have udev and modalias rules where the git repo has a .so , is that expected? if there is no binary content why do you have those depends?

libglib2.0-0 (>= 2.14.0), libusb-1.0-0 (>= 2:1.0.9), libfprint-2-2 (>= 1.90.1), libfprint-2-tod1 (>= 1.90.1)

libfprint-2-tod1-goodix has been uploaded to oem-archive for certified platform, it's not blocking the user to use the device. Lower the priority to Low.

The package in http://oem.archive.canonical.com/pool/public/libf/libfprint-2-tod1-goodix/ indeed looks better and has contents (ships .so, and hence the binary deps).

The one in the queue looks incomplete, and I guess should be rejected, as it is effectively empty.

unsubscribing sponsors until the review questions are addressed

+subscribe sponsor

Hello @seb128,
I removed libglib2.0-0 and libusb-1.0-0 in depends since both of them depends on libfprint-2-2 and libfprint-2-tod1. I uploaded here https://launchpad.net/~andch/+archive/ubuntu/staging-fprint/+packages.

Status changed to 'Confirmed' because the bug affects multiple users.

It's been 1.5 years since the last update to the bug, and the package is targeted at focal for which it has the wrong version number.

Please resubmit a package for mantic if that's still needed and resubscribe. Presumably there's a newer upstream version available too, and all validation back on focal surely is invalidated now?

Hi @juliank,
Is that possible we only support Jammy and Focal?

Given the proprietary nature that does seem reasonable as the .so would need changes otherwise, ultimately that will be up to the SRU team to decide.

Please ensure that there's something to upload, follow the procedure in https://wiki.ubuntu.com/StableReleaseUpdates to prepare a stable release update, mostly filling out the template, and resubscribe ubuntu-sponsors when done.

@andy,

 Cause goodix provide another 0.0.10 '.so' file for 550a fingerprint, do you prepare to package these two '.so' together or separate to a single package?

 I packed a libfprint-2-tod1-goodix-550a for testing, it works fine in 22.04.

 https://launchpad.net/~libfprint-tod1-group/+archive/ubuntu/ppa/+files/libfprint-2-tod1-goodix-550a_0.0.10+2204-0ubuntu2_amd64.deb

https://launchpad.net/~libfprint-tod1-group/+archive/ubuntu/ppa

Tested the Goodix driver on ThinkPad E14 Gen 4, it cause the fprintd coredump on 20.04.6, need feedback to Goodix about this issue, and it works fine on jammy.

u-ThinkPad-E14-Gen-4 fprintd[1473]: fprintd: ../nptl/pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed.
u-ThinkPad-E14-Gen-4 systemd[1]: fprintd.service: Main process exited, code=dumped, status=6/ABRT
u-ThinkPad-E14-Gen-4 systemd[1]: fprintd.service: Failed with result 'core-dump'.

u@u-ThinkPad-E14-Gen-4:~$ lsusb
Bus 003 Device 002: ID 27c6:550a Shenzhen Goodix Technology Co.,Ltd. FingerPrint

u@u-ThinkPad-E14-Gen-4:~$ sudo add-apt-repository ppa:libfprint-tod1-group/ppa
[sudo] password for u:

u@u-ThinkPad-E14-Gen-4:~$ ubuntu-drivers list
libfprint-2-tod1-goodix-550a

u@u-ThinkPad-E14-Gen-4:~$ apt-cache policy libfprint-2-tod1-goodix-550a
libfprint-2-tod1-fpc:
Installed: 0.0.10+2004-0ubuntu2
Candidate: 0.0.10+2004-0ubuntu2

OS: 20.04.6
Kernel: 5.15.0-75-generic