lp:libfprint

Created by Registry Administrators on 2012-07-16 and last modified on 2019-12-05
Get this branch:
bzr branch lp:libfprint

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Registry Administrators
Project:
libfprint
Status:
Development

Import details

Import Status: Reviewed

This branch is an import of the HEAD branch of the Git repository at git://anongit.freedesktop.org/libfprint/libfprint.

The next import is scheduled to run in 3 hours.

Last successful import was 2 hours ago.

Import started 2 hours ago on alnitak and finished 2 hours ago taking 25 seconds — see the log
Import started 8 hours ago on izar and finished 8 hours ago taking 20 seconds — see the log
Import started 14 hours ago on alnitak and finished 14 hours ago taking 20 seconds — see the log
Import started 20 hours ago on alnitak and finished 20 hours ago taking 25 seconds — see the log
Import started on 2019-12-04 on izar and finished on 2019-12-04 taking 15 seconds — see the log
Import started on 2019-12-04 on izar and finished on 2019-12-04 taking 20 seconds — see the log
Import started on 2019-12-04 on alnitak and finished on 2019-12-04 taking 25 seconds — see the log
Import started on 2019-12-03 on alnitak and finished on 2019-12-03 taking 25 seconds — see the log
Import started on 2019-12-03 on alnitak and finished on 2019-12-03 taking 20 seconds — see the log
Import started on 2019-12-03 on alnitak and finished on 2019-12-03 taking 25 seconds — see the log

Recent revisions

838. By Benjamin Berg <email address hidden> 3 hours ago

print: Fix match error propagation

The FPI_MATCH_ERROR constant was set to 0, however it is propagated to
the task completion using g_task_propagate_int. As g_task_propagate_int
will always return -1 on error, we either need to add an explicit -1
check or we just need to match the semantics.

Change the constant to -1, also rearange FP_MATCH_SUCCESS so that it
does not end up being 0.

837. By Benjamin Berg <email address hidden> 18 hours ago

tests: Test finger removal after minutiae scan completion

836. By Benjamin Berg <email address hidden> 18 hours ago

tests: Update helper functions for new virtual-image features

This also changes the code to keep the connection open and adds
automatic mainloop iteration to ensure the driver processes the request.
This is important so we will not deadlock when we send multiple
requests.

835. By Benjamin Berg <email address hidden> 18 hours ago

virtual-image: Allow fine control over the finger state

Add commands to disable automatic finger reporting for images and to
send a specific finger report. This is useful to test more code paths
inside the image-device code.

834. By Benjamin Berg <email address hidden> 18 hours ago

virtual-image: Only print warnings for actual errors

No need to warn for lost connections (if we don't expect more data) or
cancellations.

833. By Benjamin Berg <email address hidden> 18 hours ago

image-device: Print warning for incorrect deactivation

Drivers may not handle deactivation properly when they are awaiting a
finger. This should be prevented by the internal FpImageDevice state
machine.

832. By Marco Trevisan (Treviño) 19 hours ago

vfs0051: Use named SSMs for usb async exchanges

831. By Marco Trevisan (Treviño) 19 hours ago

fpi-ssm: Improve debugging of SSM using driver infos

Always mention the driver that is triggering it

830. By Marco Trevisan (Treviño) 19 hours ago

fpi-ssm: Support named SSMs and use a fallback macro

Add fpi_ssm_new_full() that allows to pass a name to the state-machine
constructor, not to change all the drivers, provide a fpi_ssm_new() macro
that stringifies the nr_parameters value (usually an enum value) as the name
so that we can use it for better debugging.

829. By Marco Trevisan (Treviño) 19 hours ago

ci: Build flatpak automatically only on master and tagso

While allowing to build it manually in other cases

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
This branch contains Public information 
Everyone can see this information.