4f85d9e1b3
debian/patches: Don't byte-swap two times the NBIS print array contents
...
Fixes virtual-image test in libfprint for s390x
2020-12-02 17:48:28 +01:00
f58ac0a499
debian/patches: Properly handle identify return value and add tests
...
This fixes fprintd test failures in s390x
2020-12-02 17:47:37 +01:00
de271a0e8d
fp-print: Don't byte-swap two times the NBIS array contents
...
When serializing an image print in big endian machine we ended up
swapping the arrays contents two times, first when adding the values and
eventually when calling g_variant_byteswap which already handles this
properly.
With this, we get the test passing into s390x.
Fixes : #236
2020-12-02 16:40:10 +00:00
12b0120a3d
test-fpi-device: Always check the return values for the API calls
...
Ensure that the return value of the API calls match the expected one,
as we need to ensure that it also matches with the error/no-error case.
2020-12-02 16:28:36 +00:00
2783ac3e60
fpi-device: Return proper type on identification success
...
Identify function is supposed to propagate a boolean value, but we make
it return an integer instead on idle, this can be normally the same in
most of architectures, but not in BE ones.
So, make it return the proper type.
Fixes test failures in s390x.
Related to #236
2020-12-02 16:28:36 +00:00
5cc6a64502
Upload to unstable
2020-12-02 05:11:33 +01:00
6a22714677
Update changelog
2020-12-02 05:09:33 +01:00
457f8c818c
debian/patches: Use gbp pq topics for debian-specific patches
2020-12-02 05:09:33 +01:00
e696d77514
New upstream release
2020-12-02 04:57:16 +01:00
c083be9ed6
Update upstream source from tag 'upstream/1.90.5'
...
Update to upstream version '1.90.5'
with Debian dir af3de02221
2020-12-02 04:53:48 +01:00
5f93ff8536
New upstream version 1.90.5
2020-12-02 04:53:44 +01:00
abb0b1267c
synaptics: add support PID 0xE7
2020-12-02 10:21:39 +08:00
90f41d13a0
debian/control: Mark libfprint-2-dev as Multi-Arch: same
2020-12-01 12:12:25 +01:00
d44b1bacbd
Release to unstable
2020-12-01 11:38:38 +01:00
82286e7496
debian/control: Bump Standards-Version to 4.5.1 (no further changes)
2020-12-01 11:35:11 +01:00
efa3c0cbb9
Merge branch 'debian' into 'debian'
...
Update to libfprint 1.90.4
See merge request debian/libfprint!4
2020-12-01 10:29:12 +00:00
5cb91a4189
Release 1.90.5
2020-12-01 10:14:26 +01:00
0bb132b167
NEWS: Fix release date of 1.90.4
2020-12-01 10:14:02 +01:00
ce39f27b5e
vfs301_proto: Remove usless break after return
...
Closes : #341
2020-11-30 20:22:18 +00:00
7d0956513b
upekts: Remove duplicated err handling path
...
Closes : #342
2020-11-30 20:22:17 +00:00
4d978f23d1
debian/rules: Also build the virtual drivers, as they're useful for testing
2020-11-30 20:28:48 +01:00
f59e608351
Update changelog
2020-11-30 20:25:35 +01:00
c8503f301a
Update changelog
2020-11-30 20:24:37 +01:00
2866d8a247
debian/patches: Reorder to give upstream more priority
2020-11-30 20:24:11 +01:00
0c9f7cf5ea
debian/patches: Don't use power-save mode for USB controller
...
LP: #1906296
2020-11-30 20:14:09 +01:00
2b7cfa751a
list-udev-rules: Remove Wrongly added well-known USB controller vid/pid combo
...
This was causing USB controllers to use power-saving mode, breaking usb
devices usage.
Related to: https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/327
2020-11-30 20:03:32 +01:00
b27542b02e
Update changelog
2020-11-30 19:58:52 +01:00
0eee6a56dd
synaptics: add support to sensor PID 0xC9
2020-11-30 13:53:07 +08:00
c595b5b170
debian/libfprint-2-2.symbols: Add new symbols
2020-11-27 16:48:03 +01:00
71676bd2e8
debian/rules: Also build the virtual drivers, as they're useful for testing
...
Mostly it allows testing fprintd fully.
2020-11-27 16:35:08 +01:00
aff0fe6553
Update upstream source from tag 'upstream/1.90.4'
...
Update to upstream version '1.90.4'
with Debian dir 1ef71fb7ce
2020-11-27 16:28:28 +01:00
480451d784
New upstream version 1.90.4
2020-11-27 16:28:21 +01:00
8962e14fde
Release 1.90.4
2020-11-27 13:55:49 +01:00
e246e00ba3
elan: added 0c4d device to the array of supported devices
2020-11-26 12:39:19 +01:00
8ab27bb03f
Finalise changelog
2020-11-25 19:18:20 +01:00
bdaf73c01d
Update changelog
2020-11-25 19:17:58 +01:00
aa75b6f027
debian/patches: Add identification support to synaptics driver
...
It allows to unlock / log-in with any finger.
LP: #1905600
2020-11-25 19:04:33 +01:00
e8d6f1bd01
debian/patches: Ensure we do not waste power for unsupported devices
...
LP: #1905603
2020-11-25 19:04:33 +01:00
3c35c01af9
debian/patches: Fix vfs301 verification using device pointer on callbacks
...
LP: #1905597
2020-11-25 18:56:26 +01:00
576beb1ff5
debian/patches: Add support for new Synaptics devices IDs
...
LP: #1905593
2020-11-25 18:56:08 +01:00
fa3bdb874d
udev-rules: Regenerate from wiki to include VFS495
2020-11-25 18:28:41 +01:00
32767f4e16
debian/patches: Properly handle aes3k devices, resubmitting commands
...
This also needs proper commands cancellation
LP: #1897613
2020-11-25 18:15:09 +01:00
e4d2eaeff7
debian/patches: Refresh
2020-11-25 18:15:05 +01:00
de761cd741
debian/gbp.conf: Include debian's GNOME team preferred settings
2020-11-25 18:06:51 +01:00
2caeb8cbb3
udev-rules: Add unsupported devices from wiki page to rules
...
This ensures we are putting all these devices (which are unusable) into
power save mode.
2020-11-25 14:56:06 +00:00
dda3587b76
identify: Use stored print to show identify information
...
The stored print may contain more metadata, so let's use that for
device-stored print, if available.
2020-11-23 17:00:01 +00:00
fb5854213a
examples: Add Identify example
...
It was the only main action left in the examples, we use the gallery
from the device if available, otherwise the local one.
2020-11-23 17:00:01 +00:00
21ee241f0c
virtual-image: Add command to trigger device removal
...
This is primarily useful for fprintd testing.
2020-11-23 17:47:03 +01:00
280f916ace
image-device: Fix incorrect g_free of error
...
GError needs to be free'ed using g_error_free, fix this.
2020-11-23 17:47:03 +01:00
1b5dd0057f
tests: Add device removal test
...
This tests all relevant scenarios of device removal, i.e.:
* device is not open
* device is currently closing
* device is open and idle
* device is currently opening
* device is open and active
The test ensures that in all scenarios the following holds true:
* device "removed" signal is only emitted after the action completes
* context "device-removed" signal is only emitted after the device has
been closed
Note that the "opening" case is special. Here we confirm that a success
from "open" will not be overriden by a FP_DEVICE_ERROR_REMOVED error, in
order to correctly signal that the internal device state is open and it
needs to be closed.
2020-11-23 17:47:03 +01:00
Marco Trevisan (Treviño)