https://bugs.kde.org/show_bug.cgi?id=450859
--- Comment #14 from espi...@gmail.com ---
(In reply to maximilian from comment #13)
> (In reply to espidev from comment #12)
> > (In reply to maximilian from comment #10)
> > > Is there a more light way but installing gnome?
> > > (In reply to espidev from comment #9)
> > > > I recommend doing a quick check with another implementation that uses
> > > > the
> > > > fprint dbus API (ex. GNOME's interface) to see if the same issue occurs,
> > > > perhaps this is an issue for that fprint implementation to fix.
> >
> > I guess another way you can test is by:
> > -> Open system settings and the fingerprint dialog, and leave it open when
> > following further steps
> > -> Open QDBusViewer (an app)
> > -> Go to System Bus
> > -> go to "net.reactivated.Fprint" on the left pane
> > -> on the right bay, navigate the methods to
> > "net/reactivated/Fprint/Device/0/net.reactivated.Fprint.Device"
> > -> double click on "Method: ListEnrolledFingers"
> > -> enter your username, and see what the reply is on the bottom pane
> >
> > I get:
> >
> > Received reply from :1.5423
> > Arguments: {"right-little-finger", "right-ring-finger",
> > "right-middle-finger", "right-index-finger"}
>
> Thanks for your reply!
> This is my output:
> Connected to D-Bus.
>
> Received reply from :1.20
> Arguments: {"WINBIO_ANSI_381_POS_RH_INDEX_FINGER"}
It seems python-validity/open-fprintd is giving fingerprint names not listed in
the fprint API specification:
https://fprint.freedesktop.org/fprintd-dev/Device.html#fingerprint-names
I think this issue should be addressed from their side.
--
You are receiving this mail because:
You are watching all bug changes.
