fprint hangs after first finger scan (fprintd-enroll) with AES3500

Thank you for the report, it sounds like Marco requested for the launchpad bug so I'm assigning to him

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

---------------
libfprint (1:1.90.3+tod1-0ubuntu2) hirsute; urgency=medium

  * debian/gbp.conf: Include debian's GNOME team preferred settings
  * debian/patches (upstream cherry-picks):
    - Properly handle aes3k devices, resubmitting commands.
      This also needs proper commands cancellation (LP: #1897613)
    - Add support for new Synaptics devices IDs (LP: #1905593)
    - Fix vfs301 verification using device pointer on callbacks (LP: #1905597)
    - Ensure we do not waste power for unsupported devices (LP: #1905603)
    - Add identification support to synaptics driver.
      It allows to unlock / log-in with any finger. (LP: #1905600)

 -- Marco Trevisan (Treviño) <email address hidden> Wed, 25 Nov 2020 19:18:20 +0100

Hello Federico, or anyone else affected,

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

Hello Federico, 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.3 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.

Hello, the problem seems not fixed, but I'm not really sure how to debug it now.

$ lsb_release -a
LSB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
Distributor ID: Ubuntu
Description: Ubuntu 20.10
Release: 20.10
Codename: groovy

I open settings and try to add a fingerprint to a user, after the first try nothing happens anymore.

This is lsof with the fingerprint enrolling open (I should be using the right library)

:~$ sudo lsof -n | grep fprint
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1001/gvfs
      Output information may be incomplete.
lsof: WARNING: can't stat() fuse.portal file system /run/user/1001/doc
      Output information may be incomplete.
gnome-con 9559 federico mem REG 259,3 6677 11012760 /usr/share/locale-langpack/it/LC_MESSAGES/fprintd.mo
gnome-con 9559 9560 gmain federico mem REG 259,3 6677 11012760 /usr/share/locale-langpack/it/LC_MESSAGES/fprintd.mo
gnome-con 9559 9561 gdbus federico mem REG 259,3 6677 11012760 /usr/share/locale-langpack/it/LC_MESSAGES/fprintd.mo
gnome-con 9559 9562 gnome-c:d federico mem REG 259,3 6677 11012760 /usr/share/locale-langpack/it/LC_MESSAGES/fprintd.mo
gnome-con 9559 9563 gnome-c:d federico mem REG 259,3 6677 11012760 /usr/share/locale-langpack/it/LC_MESSAGES/fprintd.mo
gnome-con 9559 9564 gnome-c:d federico mem REG 259,3 6677 11012760 /usr/share/locale-langpack/it/LC_MESSAGES/fprintd.mo
gnome-con 9559 9565 gnome-c:d federico mem REG 259,3 6677 11012760 /usr/share/locale-langpack/it/LC_MESSAGES/fprintd.mo
gnome-con 9559 9567 pool-gnom federico mem REG 259,3 6677 11012760 /usr/share/locale-langpack/it/LC_MESSAGES/fprintd.mo
gnome-con 9559 9569 dconf\x20 federico mem REG 259,3 6677 11012760 /usr/share/locale-langpack/it/LC_MESSAGES/fprintd.mo
gnome-con 9559 9570 pool-gnom federico mem REG 259,3 6677 11012760 /usr/share/locale-langpack/it/LC_MESSAGES/fprintd.mo
gnome-con 9559 9571 threaded- federico mem REG 259,3 6677 11012760 /usr/share/locale-langpack/it/LC_MESSAGES/fprintd.mo
fprintd 9580 root cwd DIR 259,3 4096 2 /
fprintd 9580 root rtd DIR 259,3 4096 2 /
fprintd 9580 root txt REG 259,3 63872 9968048 /usr/libexec/fprintd
fprintd 9580 root mem REG 259,3 22600 25035636 /lib/x86_64-linux-gnu/libkeyutils.so.1.9
fprintd 9580 root mem REG 259,3 56112 9962574 /usr/lib/x86_64-linux-gnu/libkrb5support.so.0.1
fprintd 9580 root mem REG 259,3 191040 9974920 /usr/lib/x86_64-linux-gnu/libk5c...

Can you please provide the output for:
 apt-cache policy libfprint-2-2

?

Sure:
:~$ apt-cache policy libfprint-2-2
libfprint-2-2:
  Installato: 1:1.90.3+tod1-0ubuntu2~20.10.1
  Candidato: 1:1.90.3+tod1-0ubuntu2~20.10.1
  Tabella versione:
 *** 1:1.90.3+tod1-0ubuntu2~20.10.1 500
        500 http://it.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     1:1.90.3+tod1-0ubuntu1 500
        500 http://it.archive.ubuntu.com/ubuntu groovy/main amd64 Packages

Ah, you're in groovy...

Weird, as I've included all the related patches that were in https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/306 (and the test that Ben did using your prints passed).

To get some useful information, please add this

 Environment=G_MESSAGES_DEBUG=all

Under the [Service] stanza of /lib/systemd/system/fprintd.service

Then run

  journalctl --service fprint.service

And start the enrollment process again (you can use also fprintd-enroll / fprintd-verify from command line)

Use

journalctl --service fprint.service -ef

To follow the log

added, here the journalctl

dic 02 18:04:41 federico-XPS systemd[1]: Starting Fingerprint Authentication Daemon...
dic 02 18:04:41 federico-XPS fprintd[27711]: About to load configuration file '/etc/fprintd.conf'
dic 02 18:04:41 federico-XPS fprintd[27711]: Launching FprintObject
dic 02 18:04:41 federico-XPS fprintd[27711]: No driver found for USB device 1D6B:0003
dic 02 18:04:41 federico-XPS fprintd[27711]: No driver found for USB device 1D6B:0002
dic 02 18:04:41 federico-XPS fprintd[27711]: No driver found for USB device 1D6B:0003
dic 02 18:04:41 federico-XPS fprintd[27711]: No driver found for USB device 0C45:670C
dic 02 18:04:41 federico-XPS fprintd[27711]: No driver found for USB device 04F3:20D0
dic 02 18:04:41 federico-XPS fprintd[27711]: No driver found for USB device 8087:0A2B
dic 02 18:04:41 federico-XPS fprintd[27711]: No driver found for USB device 1D6B:0002
dic 02 18:04:41 federico-XPS systemd[1]: Started Fingerprint Authentication Daemon.
dic 02 18:04:41 federico-XPS fprintd[27711]: D-Bus service launched with name: net.reactivated.Fprint
dic 02 18:04:41 federico-XPS fprintd[27711]: entering main loop
dic 02 18:04:41 federico-XPS fprintd[27711]: user 'federico' claiming the device: 0
dic 02 18:04:41 federico-XPS fprintd[27711]: Image device open completed
dic 02 18:04:41 federico-XPS fprintd[27711]: Device reported open completion
dic 02 18:04:41 federico-XPS fprintd[27711]: Completing action FPI_DEVICE_ACTION_OPEN in idle!
dic 02 18:04:41 federico-XPS fprintd[27711]: claimed device 0
dic 02 18:04:41 federico-XPS fprintd[27711]: start enrollment device 0 finger 7
dic 02 18:04:41 federico-XPS fprintd[27711]: Activating image device
dic 02 18:04:41 federico-XPS fprintd[27711]: write 56 regs
dic 02 18:04:41 federico-XPS fprintd[27711]: all registers written
dic 02 18:04:41 federico-XPS fprintd[27711]: Image device activation completed
dic 02 18:04:41 federico-XPS fprintd[27711]: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
dic 02 18:04:43 federico-XPS fprintd[27711]: Image device reported finger status: on
dic 02 18:04:43 federico-XPS fprintd[27711]: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
dic 02 18:04:43 federico-XPS fprintd[27711]: frame header byte e0
dic 02 18:04:43 federico-XPS fprintd[27711]: frame header byte e1
dic 02 18:04:43 federico-XPS fprintd[27711]: frame header byte e2
dic 02 18:04:43 federico-XPS fprintd[27711]: frame header byte e3
dic 02 18:04:43 federico-XPS fprintd[27711]: frame header byte e4
dic 02 18:04:43 federico-XPS fprintd[27711]: frame header byte e5
dic 02 18:04:43 federico-XPS fprintd[27711]: frame header byte e6
dic 02 18:04:43 federico-XPS fprintd[27711]: frame header byte e7
dic 02 18:04:43 federico-XPS fprintd[27711]: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
dic 02 18:04:43 federico-XPS fprintd[27711]: Image device captured an image
dic 02 18:04:43 federico-XPS fprintd[27711]: Image device reported finger status: off
dic 02 18:04:43 federico-XPS fprintd[27711]: Awaiting finger on...

Hi Federico,

I've prepared some test packages in this PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4363

Can you maybe try it (they're still building at the moment though).
However give them a try, otherwise maybe you can ping me in IRC (or somewhere else) so we can try to figure out which upstream commit we're missing.

Cheers

So, looks like we miss a patch https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/52b2d1088

However the hang per sé is fixed, maybe we can consider the hang fixed and open another bug about the fact that enrollment doesn't work?

So we can unblock this release while I'm preparing a further fix

Hello Federico, or anyone else affected,

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

Hello Federico, 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.4 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.

Hi Federico,

Can you maybe test this again?

@SRU, the bug reporter isn't responding and we don't have access to the specific hardware to do the verification, we checked that there are no regressions in 1:1.90.2+tod1-0ubuntu1~20.04.4 on standard harwares/configurations used by oem and since the update fixes bugs the OEM team is waiting on we would like to see unblocked. I'm going to mark verification-done, if the fix doesn't work the bug can still be reopened for another SRU round later

Doing the same for the 1:1.90.3+tod1-0ubuntu2~20.10.2 update in 20.10

Also underlying that we've an automated test for such device and it didn't show any regression while the test ran correctly.

Normally it's a bit tricky whenever we have a bugfix that can't be verified by affected hardware. But seeing that the other fixes seemed to be verified (and .2 right around the corner), I think we can get it released as is. Thanks!

This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu2~20.10.2

---------------
libfprint (1:1.90.3+tod1-0ubuntu2~20.10.2) groovy; urgency=medium

  * debian/patches:
    - image-device: Delay completion until deactivation (LP: #1897613)
    - Support more synaptics devices PIDs (LP: #1905593)
    - Ensure we properly handle references of prints galleries (LP: #1908107)

libfprint (1:1.90.3+tod1-0ubuntu2~20.10.1) groovy; urgency=medium

  * debian/gbp.conf:
    - Include debian's GNOME team preferred settings
    - Prepare for groovy branching
  * debian/patches (upstream cherry-picks):
    - Properly handle aes3k devices, resubmitting commands.
      This also needs proper commands cancellation (LP: #1897613)
    - Add support for new Synaptics devices IDs (LP: #1905593)
    - Fix vfs301 verification using device pointer on callbacks (LP: #1905597)
    - Ensure we do not waste power for unsupported devices (LP: #1905603)
    - Add identification support to synaptics driver.
      It allows to unlock / log-in with any finger. (LP: #1905600)

 -- Marco Trevisan (Treviño) <email address hidden> Mon, 14 Dec 2020 19:19:45 +0100

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.

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

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

  * debian/patches:
    - image-device: Delay completion until deactivation (LP: #1897613)
    - Support more synaptics devices PIDs (LP: #1905593)
    - Ensure we properly handle references of prints galleries (LP: #1908107)

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

  * debian/patches (upstream cherry-picks):
    - Properly handle aes3k devices, resubmitting commands.
      This also needs proper commands cancellation (LP: #1897613)
    - Add support for new Synaptics devices IDs (LP: #1905593)
    - Fix vfs301 verification using device pointer on callbacks (LP: #1905597)
    - Ensure we do not waste power for unsupported devices (LP: #1905603)
    - Add identification support to synaptics driver.
      It allows to unlock / log-in with any finger. (LP: #1905600)

 -- Marco Trevisan (Treviño) <email address hidden> Mon, 14 Dec 2020 19:28:09 +0100