| Summary: | Fingerprint accepted but does not appear in the list of configured fingerprints when using python-validity | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Dan Sunter <dsunter> |
| Component: | kcm_users | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | biladina102, espidev, maximilian, nate, uhhadd |
| Priority: | NOR | ||
| Version First Reported In: | 5.24.2 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| URL: | https://github.com/uunicorn/python-validity/issues/116 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | as on image, enrolled fingerprint list not showing after fingerprint added.. | ||
|
Description
Dan Sunter
2022-02-26 03:25:10 UTC
Fingerprint seems to work just doesn't show in the UI for KDE Created attachment 147132 [details]
as on image, enrolled fingerprint list not showing after fingerprint added..
(In reply to biladina from comment #2) > Created attachment 147132 [details] > as on image, enrolled fingerprint list not showing after fingerprint added.. also tested on Thinkpad P52 : Bus 001 Device 004: ID 06cb:009a Synaptics, Inc. Metallica MIS Touch Fingerprint Reader Same problem on Arch Linux and X270 Is that the actual root user you're adding fingerprints for? Or a non-root user that happens to have been given the name "root"?
Works for me with a ThinkPad X1 Yoga G4 with this hardware:
> Bus 001 Device 032: ID 06cb:00bd Synaptics, Inc. Prometheus MIS Touch Fingerprint Reader
Which version of fprintd is installed? Is this fprintd, or something else, like python-validity? In my case python-validity with open-fprintd (In reply to espidev from comment #6) > Which version of fprintd is installed? Is this fprintd, or something else, > like python-validity? (In reply to maximilian from comment #7) > In my case python-validity with open-fprintd > (In reply to espidev from comment #6) > > Which version of fprintd is installed? Is this fprintd, or something else, > > like python-validity? I suspect that whatever is supplying the dbus api isn't behaving the same as fprintd. I vaguely recall someone having the same issue on the original MR, when they used python-validity. 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. 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 am using python-validity as well. (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"} (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"} (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. Can folks file bug reports for those projects, and link them here? (In reply to Nate Graham from comment #15) > Can folks file bug reports for those projects, and link them here? https://github.com/uunicorn/python-validity/issues/116 (In reply to espidev from comment #16) > (In reply to Nate Graham from comment #15) > > Can folks file bug reports for those projects, and link them here? > > https://github.com/uunicorn/python-validity/issues/116 Thx! |