[fprint] Upek Touchstrip (147e:1000) new driver problem

[Bastien Nocera]

On Mon, 2010-09-20 at 22:20 +0200, Hugo "Bonstra" Grostabussiat wrote:
> On 09/20/2010 19:36, Hugo "Bonstra" Grostabussiat wrote:
> >  On 09/20/2010 05:11, The Source wrote:
> >> /With enroll and verify I really wasn't getting 'try again', like you //said./
> > Okay, the cause of this never-ending try-again messages comes from a bug
> > in fprintd. I will report it.
> Bug report is here:
> https://bugs.freedesktop.org/show_bug.cgi?id=30287

It's a bug in the driver, not in fprintd. The verify-status signal is
sent when the daemon receives a callback from the driver for the verify
function. This must mean that the driver is working from old data, or
didn't actually read any data from the device.