GitLab

The device is already handled by upektc_img driver, and its sources
still exist in git if needed.

https://bugs.freedesktop.org/show_bug.cgi?id=106514

Fix "function declaration isn’t a prototype" warning

In case NSS isn't available.

https://bugs.freedesktop.org/show_bug.cgi?id=106278

Mark Harfouche authored Mar 11, 2018 and Bastien Nocera committed Mar 11, 2018

nbis/mindtct/morph.c:152:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
nbis/mindtct/morph.c:176:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
nbis/mindtct/morph.c:200:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]
nbis/mindtct/morph.c:222:4: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation]

https://bugs.freedesktop.org/show_bug.cgi?id=105429

Mark Harfouche authored Mar 11, 2018 and Bastien Nocera committed Mar 11, 2018

https://bugs.freedesktop.org/show_bug.cgi?id=105427

Mark Harfouche authored Mar 10, 2018 and Bastien Nocera committed Mar 11, 2018

libusb_free_device_list() needs to be called on the list of USB devices
obtained through libusb_get_device_list() or the list and its elements
will be leaked.

https://bugs.freedesktop.org/show_bug.cgi?id=105427

Hans de Goede authored Dec 12, 2017 and Bastien Nocera committed Dec 12, 2017

Remove 2 entries from the whitelist for finger-print models for which
we have a driver now, so they no longer need to be on the whitelist.

Otherwise we get false positives on devices without encryption

Add naive detection of image encryption: if stddev between two
adjacent rows is higher than threshold assume that image is encrypted
and decrypt it.

Fixes fd.o bug 88945

Its width is only 216 pixels, and it appears not to be enough for matching at
default threshold.

Use fpi_mean_sq_diff_norm() for blank line detection and
fpi_mean_sq_diff_norm() for duplicate line detection.
Fixes finger presence and removal detection.

Konstantin Semenov authored Jan 19, 2016 and Vasily Khoruzhick committed Nov 05, 2016

New driver for 138a:0050 device

https://bugs.freedesktop.org/show_bug.cgi?id=91616

The code was indented, but only the first call was actually in the
conditional, which meant that initialisation carried on as normal on top
of a failed USB device. Exit early and remove the conditional to fix
this.

https://bugzilla.gnome.org/show_bug.cgi?id=98594

The code was indented, but only the first call was actually in the
conditional, which meant that initialisation carried on as normal on top
of a failed USB device. Exit early and remove the conditional to fix
this.

https://bugs.freedesktop.org/show_bug.cgi?id=98594

Debian's ash doesn't implement pushd/popd.

The device is already supported by the vfs5011 driver and non-
blacklisted, so will show up in the udev rules, but for ease of
backporting to older versions, add it to the whitelist anyway.

https://bugzilla.redhat.com/show_bug.cgi?id=1173367

Driver is not able to cancel imaging process without this change

It was here for aes2501 and aes1610 before moving assembling routines
into common code.

Height is not a good determinant in movement direction, normalized
error is much better. Should fix aes1610 and aes2501 driver issues.

Set partial flag to remove false minutiae at the perimeter of a scan

Set partial flag to remove false minutiae at the perimeter of a scan

Set partial flag to remove false minutiae at the perimeter of a scan

Set partial flag to remove false minutiae at the perimeter of a scan