0688288c6d
.git-blame-ignore-revs: Ignore formatting commit and add hint how to use it
2020-12-07 19:01:10 +01:00
c1e832e7a7
fp-device: Return valid finger status value on error
...
Not that the two enums have different value, but indeed the type is
wrong.
2020-12-04 12:15:22 +00:00
b5496fd257
fp-device: Ensure finger status is set to proper type on property getter
...
Finger status is a flag not an enum.
Add tests.
2020-12-04 12:15:22 +00:00
bb38a8c99c
debian/gbp.conf: Include suggested settings by GNOME team
...
Even if libfprint is not part of GNOME I think these settings are good
practice anyways.
2020-12-02 21:16:41 +01:00
cb0eb5c5be
debian/rules: Increase testing timeout
...
As default might not be enough in some archs
2020-12-02 20:58:21 +01:00
776c789533
debian: Switch to debhelper 13 and use its features
...
As per this restrict more the .install files wilcards
2020-12-02 20:58:21 +01:00
899d5c309f
debian/rules: Enable tests in s390x as it now builds and tests correctly
2020-12-02 19:01:08 +01:00
632a2abf62
Upload to unstable
2020-12-02 17:53:32 +01:00
616dbcaad6
Update changelog
2020-12-02 17:52:57 +01:00
0494815d57
Add myself to Uploaders
2020-12-02 17:52:11 +01:00
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
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
fa3bdb874d
udev-rules: Regenerate from wiki to include VFS495
2020-11-25 18:28:41 +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
8a6f1932f8
virtual-image: Add a notify::removed handler
...
In general, we rely on the underlying transport layer to throw errors
which will abort the current operation. This does not work for the
virtual image device though, but we need it there for testing purposes.
Add a notify::removed handler that makes things work as expected. Let it
throw a protocol error which should not be visible to the outside.
2020-11-23 17:47:03 +01:00
0051ff6352
device: Treat devices as closed even after a close failure
...
We require the close call, but as the underlying transport layer is
gone, it will generally just return an error.
In principle, it makes sense to think of close as a function that always
succeeds (i.e. it makes no sense to try again). Should the device be in
a bad state, then a subsequent open() will simply fail.
2020-11-23 17:47:03 +01:00
b6dd522459
Rework device removal to have a nice API
...
This enhances the device removal to create a well defined behaviour.
Primarily, it means that:
* "device-removed" will only be called for closed devices
* "removed" will be called only when no operation is active
Note that all actions will fail with FP_DEVICE_ERROR_REMOVED, *except*
for open which will only return this error if it failed.
Resolves : #330
2020-11-23 17:47:03 +01:00
656bf3d175
elan: Add a few comments that stopping/callibrating helps
...
Apparently stopping/callibrating helps with the reliability of these
sensors. Add a few comments so that this information is known.
See https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/216#note_619467
2020-11-18 15:18:11 +01:00
Marco Trevisan (Treviño)