https://bugs.kde.org/show_bug.cgi?id=454686
ratijas <m...@ratijas.tk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |RESOLVED
Resolution|FIXED |UPSTREAM
--- Comment #6 from ratijas <m...@ratijas.tk> ---
As I was investigating implementation of fprint, I found that it is actually a
enum of two variants.
/**
* FpScanType:
* @FP_SCAN_TYPE_SWIPE: Sensor requires swiping the finger.
* @FP_SCAN_TYPE_PRESS: Sensor requires placing/pressing down the finger.
*/
typedef enum {
FP_SCAN_TYPE_SWIPE,
FP_SCAN_TYPE_PRESS,
} FpScanType;
This scan type is proxy-passed via D-Bus to the users / enrollment KCM (system
settings module), and used in the label accordingly:
kde/workspace/plasma-workspace/kcms/users/package/contents/ui/FingerprintDialog.qml:137:
text: i18nc("%1 is a type of operation (e.g. 'scan') and %2 is
the name of a finger", "Please repeatedly %1 your %2 on the fingerprint
sensor.", fingerprintModel.scanType,
fingerprintRoot.currentFinger.toLowerCase())
So if you really believe that the wrong action is suggested for your device,
then it's worth looking into its libfprint driver first. And for that you need
to find out the exact model you have :)
You can then file a bug report at libfprint project here:
https://gitlab.freedesktop.org/libfprint/libfprint/-/issues
--
You are receiving this mail because:
You are watching all bug changes.
