[fprint] Planning libfprint API changes (2.x)

[Peter Maatman]

Hey,

I've just tested the etes603 driver. There seem to be some issues
with the cancelling which I'll investigate further this weekend.
Seems to have to do with not closing the device properly after
the cancellation, after which the gtk test program segfaults
when you try to start a new capture.

- Peter



On Wed, Jul 10, 2019 at 2:24 PM Benjamin Berg <benjamin at sipsolutions.net>
wrote:

> Hey,
>
> On Wed, 2019-07-10 at 14:21 +0200, Bastien Nocera wrote:
> > > … Most drivers have been ported at this point (fixing a
> > > number of issues in the process).
> >
> > Anything that could be backported? Failing that, an issue filed per
> > problem would go a long way towards cleanups for 1.0.
>
> There were a few places with e.g. large memory leaks or even things
> that looked suspiciously like out of bounds memory writes.
>
> Does it sound good to you if I create a private ticket for a start and
> write down some of the major pain points (before I forget about where
> it was again)?
>
> Benjamin
> _______________________________________________
> fprint mailing list
> fprint at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/fprint
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/fprint/attachments/20190710/c30beb7a/attachment.html>