libfprint issueshttps://gitlab.freedesktop.org/libfprint/libfprint/-/issues2023-02-25T18:39:23Zhttps://gitlab.freedesktop.org/libfprint/libfprint/-/issues/546Fingerprint not supported on the on linux mint 21.12023-02-25T18:39:23ZEvans Kiptarus KibetFingerprint not supported on the on linux mint 21.1When i run the command:
`fprintd-enroll`
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices availableWhen i run the command:
`fprintd-enroll`
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices availablehttps://gitlab.freedesktop.org/libfprint/libfprint/-/issues/545[macOS] disable SPI to compile2023-09-23T14:37:26ZThéo FORTIN[macOS] disable SPI to compile# macOS support
Hey I'm looking for a new way to authenticate on macOS devices.
macOS does not use udev, therefore, no spi.
Is there a quick way to assess this issue and disable SPI for the build and then for the compiler ?
My Mac is an ...# macOS support
Hey I'm looking for a new way to authenticate on macOS devices.
macOS does not use udev, therefore, no spi.
Is there a quick way to assess this issue and disable SPI for the build and then for the compiler ?
My Mac is an Intel hackintosh running macOS 13.2 (Ventura)
## Expeted behavior
Builds without SPI support
## Observed behavior
Doesn't build
## What I've done
### meson.build
Line 131
```diff
- 'elanspi',
+ #'elanspi',
```
Line 160
```diff
- 'elanspi' : [ 'udev' ],
+ #'elanspi' : [ 'udev' ],
```
Which permitted me to configure the project.
## The error
Whenever I'm trying to build the code, I get these results :
```
INFO: autodetecting backend as ninja
INFO: calculating backend command to run: /usr/local/bin/ninja
[37/129] Linking static target libfprint/libnbis.a
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: libfprint/libnbis.a(nbis_bozorth3_bz_alloc.c.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: libfprint/libnbis.a(nbis_mindtct_link.c.o) has no symbols
[38/129] Compiling C object libfprint/libfprint-private.a.p/fpi-image.c.o
../libfprint/fpi-image.c:123:82: warning: cast from 'guint8 *' (aka 'unsigned char *') to 'uint32_t *' (aka 'unsigned int *') increases required alignment from 1 to 4 [-Wcast-align]
orig = pixman_image_create_bits (PIXMAN_a8, orig_img->width, orig_img->height, (uint32_t *) orig_img->data, orig_img->width);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.
[39/129] Compiling C object libfprint/libfprint-private.a.p/meson-generated_.._fpi-enums.c.o
In file included from libfprint/fpi-enums.c:18:
../libfprint/fpi-spi-transfer.h:30:32: warning: redefinition of typedef 'FpiSsm' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSsm FpiSsm;
^
../libfprint/fpi-usb-transfer.h:34:32: note: previous definition is here
typedef struct _FpiSsm FpiSsm;
^
In file included from libfprint/fpi-enums.c:19:
../libfprint/fpi-ssm.h:35:24: warning: redefinition of typedef 'FpiSsm' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSsm FpiSsm;
^
../libfprint/fpi-spi-transfer.h:30:32: note: previous definition is here
typedef struct _FpiSsm FpiSsm;
^
In file included from libfprint/fpi-enums.c:19:
../libfprint/fpi-ssm.h:104:32: warning: redefinition of typedef 'FpiUsbTransfer' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiUsbTransfer FpiUsbTransfer;
^
../libfprint/fpi-usb-transfer.h:33:32: note: previous definition is here
typedef struct _FpiUsbTransfer FpiUsbTransfer;
^
In file included from libfprint/fpi-enums.c:19:
../libfprint/fpi-ssm.h:115:32: warning: redefinition of typedef 'FpiSpiTransfer' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSpiTransfer FpiSpiTransfer;
^
../libfprint/fpi-spi-transfer.h:29:32: note: previous definition is here
typedef struct _FpiSpiTransfer FpiSpiTransfer;
^
4 warnings generated.
[44/129] Compiling C object libfprint/libfprint-private.a.p/fpi-spi-transfer.c.o
FAILED: libfprint/libfprint-private.a.p/fpi-spi-transfer.c.o
cc -Ilibfprint/libfprint-private.a.p -Ilibfprint -I../libfprint -I. -I.. -Ilibfprint/nbis/include -I../libfprint/nbis/include -Ilibfprint/nbis/libfprint-include -I../libfprint/nbis/libfprint-include -I/usr/local/Cellar/glib/2.74.5/include/gio-unix-2.0 -I/usr/local/Cellar/glib/2.74.5/include -I/usr/local/Cellar/glib/2.74.5/include/glib-2.0 -I/usr/local/Cellar/glib/2.74.5/lib/glib-2.0/include -I/usr/local/opt/gettext/include -I/usr/local/Cellar/pcre2/10.42/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/usr/include/ffi -I/usr/local/Cellar/libgusb/0.4.2/include/gusb-1 -I/usr/local/Cellar/libusb/1.0.26/include/libusb-1.0 -I/usr/local/Cellar/json-glib/1.6.6/include/json-glib-1.0 -I/usr/local/Cellar/pixman/0.42.2/include/pixman-1 -I/usr/local/Cellar/nss/3.88.1/include/nss -I/usr/local/Cellar/nspr/4.35/include/nspr -fcolor-diagnostics -Wall -Winvalid-pch -std=gnu99 -O2 -g -Wall -Wcast-align -Wformat-nonliteral -Wformat-security -Wformat=2 -Wignored-qualifiers -Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs -Wmissing-noreturn -Wpointer-arith -Wshadow -Wswitch-enum -Wtype-limits -Wundef -Wunused -Werror=address -Werror=array-bounds -Werror=empty-body -Werror=init-self -Werror=int-to-pointer-cast -Werror=main -Werror=missing-braces -Werror=nonnull -Werror=redundant-decls -Werror=return-type -Werror=sequence-point -Werror=trigraphs -Werror=write-strings -fno-strict-aliasing -DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_56 -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_56 -D_GNU_SOURCE '-DG_LOG_DOMAIN="libfprint"' -Wimplicit-function-declaration -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wstrict-prototypes -Werror=implicit -Werror=pointer-to-int-cast -MD -MQ libfprint/libfprint-private.a.p/fpi-spi-transfer.c.o -MF libfprint/libfprint-private.a.p/fpi-spi-transfer.c.o.d -o libfprint/libfprint-private.a.p/fpi-spi-transfer.c.o -c ../libfprint/fpi-spi-transfer.c
../libfprint/fpi-spi-transfer.c:22:10: fatal error: 'linux/spi/spidev.h' file not found
#include <linux/spi/spidev.h>
^~~~~~~~~~~~~~~~~~~~
1 error generated.
[46/129] Compiling C object libfprint/libfprint-private.a.p/fpi-ssm.c.o
In file included from ../libfprint/fpi-ssm.c:24:
In file included from ../libfprint/drivers_api.h:32:
../libfprint/fpi-spi-transfer.h:30:32: warning: redefinition of typedef 'FpiSsm' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSsm FpiSsm;
^
../libfprint/fpi-usb-transfer.h:34:32: note: previous definition is here
typedef struct _FpiSsm FpiSsm;
^
In file included from ../libfprint/fpi-ssm.c:24:
In file included from ../libfprint/drivers_api.h:33:
../libfprint/fpi-ssm.h:35:24: warning: redefinition of typedef 'FpiSsm' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSsm FpiSsm;
^
../libfprint/fpi-spi-transfer.h:30:32: note: previous definition is here
typedef struct _FpiSsm FpiSsm;
^
In file included from ../libfprint/fpi-ssm.c:24:
In file included from ../libfprint/drivers_api.h:33:
../libfprint/fpi-ssm.h:104:32: warning: redefinition of typedef 'FpiUsbTransfer' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiUsbTransfer FpiUsbTransfer;
^
../libfprint/fpi-usb-transfer.h:33:32: note: previous definition is here
typedef struct _FpiUsbTransfer FpiUsbTransfer;
^
In file included from ../libfprint/fpi-ssm.c:24:
In file included from ../libfprint/drivers_api.h:33:
../libfprint/fpi-ssm.h:115:32: warning: redefinition of typedef 'FpiSpiTransfer' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSpiTransfer FpiSpiTransfer;
^
../libfprint/fpi-spi-transfer.h:29:32: note: previous definition is here
typedef struct _FpiSpiTransfer FpiSpiTransfer;
^
4 warnings generated.
[49/129] Compiling C object libfprint/libfprint-drivers.a.p/drivers_upektc_img.c.o
In file included from ../libfprint/drivers/upektc_img.c:22:
In file included from ../libfprint/drivers_api.h:32:
../libfprint/fpi-spi-transfer.h:30:32: warning: redefinition of typedef 'FpiSsm' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSsm FpiSsm;
^
../libfprint/fpi-usb-transfer.h:34:32: note: previous definition is here
typedef struct _FpiSsm FpiSsm;
^
In file included from ../libfprint/drivers/upektc_img.c:22:
In file included from ../libfprint/drivers_api.h:33:
../libfprint/fpi-ssm.h:35:24: warning: redefinition of typedef 'FpiSsm' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSsm FpiSsm;
^
../libfprint/fpi-spi-transfer.h:30:32: note: previous definition is here
typedef struct _FpiSsm FpiSsm;
^
In file included from ../libfprint/drivers/upektc_img.c:22:
In file included from ../libfprint/drivers_api.h:33:
../libfprint/fpi-ssm.h:104:32: warning: redefinition of typedef 'FpiUsbTransfer' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiUsbTransfer FpiUsbTransfer;
^
../libfprint/fpi-usb-transfer.h:33:32: note: previous definition is here
typedef struct _FpiUsbTransfer FpiUsbTransfer;
^
In file included from ../libfprint/drivers/upektc_img.c:22:
In file included from ../libfprint/drivers_api.h:33:
../libfprint/fpi-ssm.h:115:32: warning: redefinition of typedef 'FpiSpiTransfer' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSpiTransfer FpiSpiTransfer;
^
../libfprint/fpi-spi-transfer.h:29:32: note: previous definition is here
typedef struct _FpiSpiTransfer FpiSpiTransfer;
^
4 warnings generated.
[52/129] Compiling C object libfprint/libfprint-drivers.a.p/drivers_vfs5011.c.o
In file included from ../libfprint/drivers/vfs5011.c:23:
In file included from ../libfprint/drivers_api.h:32:
../libfprint/fpi-spi-transfer.h:30:32: warning: redefinition of typedef 'FpiSsm' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSsm FpiSsm;
^
../libfprint/fpi-usb-transfer.h:34:32: note: previous definition is here
typedef struct _FpiSsm FpiSsm;
^
In file included from ../libfprint/drivers/vfs5011.c:23:
In file included from ../libfprint/drivers_api.h:33:
../libfprint/fpi-ssm.h:35:24: warning: redefinition of typedef 'FpiSsm' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSsm FpiSsm;
^
../libfprint/fpi-spi-transfer.h:30:32: note: previous definition is here
typedef struct _FpiSsm FpiSsm;
^
In file included from ../libfprint/drivers/vfs5011.c:23:
In file included from ../libfprint/drivers_api.h:33:
../libfprint/fpi-ssm.h:104:32: warning: redefinition of typedef 'FpiUsbTransfer' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiUsbTransfer FpiUsbTransfer;
^
../libfprint/fpi-usb-transfer.h:33:32: note: previous definition is here
typedef struct _FpiUsbTransfer FpiUsbTransfer;
^
In file included from ../libfprint/drivers/vfs5011.c:23:
In file included from ../libfprint/drivers_api.h:33:
../libfprint/fpi-ssm.h:115:32: warning: redefinition of typedef 'FpiSpiTransfer' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSpiTransfer FpiSpiTransfer;
^
../libfprint/fpi-spi-transfer.h:29:32: note: previous definition is here
typedef struct _FpiSpiTransfer FpiSpiTransfer;
^
4 warnings generated.
[53/129] Compiling C object libfprint/libfprint-drivers.a.p/drivers_vfs7552.c.o
In file included from ../libfprint/drivers/vfs7552.c:25:
In file included from ../libfprint/drivers_api.h:32:
../libfprint/fpi-spi-transfer.h:30:32: warning: redefinition of typedef 'FpiSsm' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSsm FpiSsm;
^
../libfprint/fpi-usb-transfer.h:34:32: note: previous definition is here
typedef struct _FpiSsm FpiSsm;
^
In file included from ../libfprint/drivers/vfs7552.c:25:
In file included from ../libfprint/drivers_api.h:33:
../libfprint/fpi-ssm.h:35:24: warning: redefinition of typedef 'FpiSsm' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSsm FpiSsm;
^
../libfprint/fpi-spi-transfer.h:30:32: note: previous definition is here
typedef struct _FpiSsm FpiSsm;
^
In file included from ../libfprint/drivers/vfs7552.c:25:
In file included from ../libfprint/drivers_api.h:33:
../libfprint/fpi-ssm.h:104:32: warning: redefinition of typedef 'FpiUsbTransfer' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiUsbTransfer FpiUsbTransfer;
^
../libfprint/fpi-usb-transfer.h:33:32: note: previous definition is here
typedef struct _FpiUsbTransfer FpiUsbTransfer;
^
In file included from ../libfprint/drivers/vfs7552.c:25:
In file included from ../libfprint/drivers_api.h:33:
../libfprint/fpi-ssm.h:115:32: warning: redefinition of typedef 'FpiSpiTransfer' is a C11 feature [-Wtypedef-redefinition]
typedef struct _FpiSpiTransfer FpiSpiTransfer;
^
../libfprint/fpi-spi-transfer.h:29:32: note: previous definition is here
typedef struct _FpiSpiTransfer FpiSpiTransfer;
^
4 warnings generated.
ninja: build stopped: subcommand failed.
```
I see that, even if the configuration is done, there is still the definitions for SPI.https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/544Template storage corrupted. Failed resetting device storage.2023-04-28T21:28:09ZMatteo PescarinTemplate storage corrupted. Failed resetting device storage.Hello all.
for reasons outside my understanding my fingerprint reader stopped working.
I'm trying to reconfigure the whole thing but I got stuck at this point:
```
$ fprintd-delete $USER
found 1 devices
Device at /net/reactivated/Fprin...Hello all.
for reasons outside my understanding my fingerprint reader stopped working.
I'm trying to reconfigure the whole thing but I got stuck at this point:
```
$ fprintd-delete $USER
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
failed to claim device: GDBus.Error:net.reactivated.Fprint.Error.Internal: Open failed with error: Package crc check failed
```
in journalctrl I'm getting the following
```
Feb 12 12:17:15 frametree fprintd[24306]: Template storage appears to have been corrupted! Error was: Corrupted message header received
Feb 12 12:17:15 frametree fprintd[24306]: A known reason for this to happen is a firmware bug triggered by another storage area being initialized.
Feb 12 12:17:15 frametree fprintd[24306]: Resetting device storage, you will need to enroll all prints again!
Feb 12 12:17:15 frametree fprintd[24306]: Reset failed: Package crc check failed
```
My current hw configuration is: Arch installation over a Framework laptop
device in use is `Bus 003 Device 012: ID 27c6:609c Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC`
(checked for fw updates and seems to be at the latest)
Let me know if you need anything else to help me debug and move forward with this.
Mat.https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/543device not recognized ELAN WBF Fingerprint Sensor ACPI\ELAN7001\4&766ADDC&0 u...2023-02-08T03:44:43Zmohamed atyadevice not recognized ELAN WBF Fingerprint Sensor ACPI\ELAN7001\4&766ADDC&0 ubuntu20.04 product: ASUSPRO P1440FAC_P1440FA
ELAN WBF Fingerprint Sensor
oem67.inf:ACPI\ELAN7001,Biometric_Install.NT
ACPI\ELAN7001\4&766ADDC&0
\_SB.PCI0.SPI0.FPRT
\Device\0000004c product: ASUSPRO P1440FAC_P1440FA
ELAN WBF Fingerprint Sensor
oem67.inf:ACPI\ELAN7001,Biometric_Install.NT
ACPI\ELAN7001\4&766ADDC&0
\_SB.PCI0.SPI0.FPRT
\Device\0000004chttps://gitlab.freedesktop.org/libfprint/libfprint/-/issues/541add support for 138a:009d Validity Sensors, Inc.2023-10-03T19:44:28Zuzurpastoradd support for 138a:009d Validity Sensors, Inc.Hi. Could you please explain why adding 138a:009d is not possible?
Fingerprint works with libfprint in the console, unfortunately without a mis-verify indicator on the device, but it works. And unfortunately it is not supported by gnome...Hi. Could you please explain why adding 138a:009d is not possible?
Fingerprint works with libfprint in the console, unfortunately without a mis-verify indicator on the device, but it works. And unfortunately it is not supported by gnome out of the box. At the least I would be happy if you could explain how to integrate my sensor into the shell.https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/540Timed out waiting for image2023-05-28T09:51:39ZMichael HeubergerTimed out waiting for imageUnable to register my fingerprint on latest Ubuntu here on my ASUS ExpertBook. Already researched everywhere and found no similar bug report.
The number one problem is this error being thrown first:
```
Feb 02 21:33:33 M1 fprintd[10412]...Unable to register my fingerprint on latest Ubuntu here on my ASUS ExpertBook. Already researched everywhere and found no similar bug report.
The number one problem is this error being thrown first:
```
Feb 02 21:33:33 M1 fprintd[10412]: Device reported an error during identify for enroll: timed out waiting for image
```
Here are more details:
```
~ ❯❯❯ lsb_release -a ✘ 130
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.10
Release: 22.10
Codename: kinetic
```
Also when I am trying to enroll my fingerprint manually like that, I'm getting an unknown error. Would be good if there is more information what the error is about:
```
~ ❯❯❯ sudo fprintd-enroll michael-heuberger
Alias tip: _ fprintd-enroll michael-heuberger
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-unknown-error
```
Any clues or suggestions what to do next? Thanks heapshttps://gitlab.freedesktop.org/libfprint/libfprint/-/issues/539Driver Request for FPC Sensor Controller2023-02-01T06:08:14ZNomaan JamalUddinDriver Request for FPC Sensor ControllerHi, I was kinda hoping I could get a driver to work with my fingerprint sensor on Xiaomi MI Notebook Ultra.
The fingerprint sensor doesn't currently seem to be supported by the libfprintd
`$ lsusb`
`Bus 003 Device 004: ID 10a5:9200 FPC...Hi, I was kinda hoping I could get a driver to work with my fingerprint sensor on Xiaomi MI Notebook Ultra.
The fingerprint sensor doesn't currently seem to be supported by the libfprintd
`$ lsusb`
`Bus 003 Device 004: ID 10a5:9200 FPC FPC Sensor Controller`https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/532Request support for Validity Sensors, Inc. VFS7552 Touch Fingerprint Sensor2022-12-24T11:56:27ZHiro DaryananiRequest support for Validity Sensors, Inc. VFS7552 Touch Fingerprint SensorHi - this is the device integrated on a Dell XPS 9365 2 in 1 laptop.
Kindly request support for thisHi - this is the device integrated on a Dell XPS 9365 2 in 1 laptop.
Kindly request support for thishttps://gitlab.freedesktop.org/libfprint/libfprint/-/issues/530Fingerprint sensors on Smart phones.2023-12-19T12:55:49ZPetr HodinaFingerprint sensors on Smart phones.Hi,
smartphones have also fingerprint scanners. They seems to work on phones with LineageOS so they are not controlled from the TrustZone. Also they are not connected through USB but over SPI.
I have looked into Oneplus 6 for Postmarke...Hi,
smartphones have also fingerprint scanners. They seems to work on phones with LineageOS so they are not controlled from the TrustZone. Also they are not connected through USB but over SPI.
I have looked into Oneplus 6 for PostmarketOS. Here's definition from the device trees:
```
goodix_fp {
compatible = "goodix,fingerprint";
interrupt-parent = <&tlmm>;
vdd-3v2-supply = <&pm8998_l22>;
vdd-voltage = <3200000 3200000>;
vdd-current = <50000>;
fp-gpio-irq = <&tlmm 121 0x00>;
fp-gpio-reset = <&tlmm 35 0x00>;
fp-gpio-enable = <&tlmm 80 0x00>;
pinctrl-names = "fp_en_init", "fp_dis_init";
pinctrl-0 = <&fp_enable_init &fp_irq_init>;
pinctrl-1 = <&fp_disable_init>;
oem,fajta;
status = "okay";
};
```
How should the libfprint interface with them?https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/523"Receive data error: USB error on device 27c6:5110 : No such device (it may h...2023-09-27T17:01:18ZAllexj"Receive data error: USB error on device 27c6:5110 : No such device (it may have been disconnected) [-4]" bunch of logs and 100% cpu usageFingerprint in my laptop (Huawei Matebook D14 2020 with Goodix fingerprint) is finally supported. Thanks the help and efforts of @mpi3d , @0x00002a and many others on ["Goodix Fingerprint Linux Development" discord server](https://disco...Fingerprint in my laptop (Huawei Matebook D14 2020 with Goodix fingerprint) is finally supported. Thanks the help and efforts of @mpi3d , @0x00002a and many others on ["Goodix Fingerprint Linux Development" discord server](https://discord.gg/XATKTUfX7M).
In order to make it work, I flashed with: https://github.com/mpi3d/goodix-fp-dump (changing in driver_51x0 the line return psk != PMK_HASH to psk == PMK_HASH)... also flash at first try fails but works at second try.
Then I installed this: https://aur.archlinux.org/packages/libfprint-goodixtls-git
And fingerprint was able to work, I can go to GNOME Settings (User settings) and set a new finger succesfully.
The problem is that it's not very usable, because I randomly get cpu 100% usage, so it's not doable. I HAD to remove my fingers because it was not a good experience.
Looking at journalctl logs, I only see A BUNCH OF:
`Receive data error: USB error on device 27c6:5110 : No such device (it may have been disconnected) [-4]`
when this bug (100% cpu) happens.
I have `libfprint-goodixtls-git r1705.3d6437b-1` installed.
Relevant merge request for this device: https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/418https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/522VFS7552 refuses to be recognized2022-11-19T21:10:06ZDunoCZVFS7552 refuses to be recognizedTried to install VFS7552 included in the test folder by adding `-D drivers=vfs7552`, sadly fprintd-enroll still doesn't see the device, how to fix this?Tried to install VFS7552 included in the test folder by adding `-D drivers=vfs7552`, sadly fprintd-enroll still doesn't see the device, how to fix this?https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/521Support for 06cb:00c4 Synaptics FS76042023-09-27T17:02:56ZTom PavelSupport for 06cb:00c4 Synaptics FS7604```
This is an HP Dragonfly laptop (8VJ56UT).
https://linux-hardware.org/?probe=2630af5372
My fingerprint sensor seems to be some slight variation on the 06cb:00c2 that is already supported.
I tested the following patch and things seem ...```
This is an HP Dragonfly laptop (8VJ56UT).
https://linux-hardware.org/?probe=2630af5372
My fingerprint sensor seems to be some slight variation on the 06cb:00c2 that is already supported.
I tested the following patch and things seem to work OK, so hopefully you can just add this device-id to the supported list.
diff --git a/libfprint/drivers/synaptics/synaptics.c b/libfprint/drivers/synaptics/synaptics.c
index f13b820..eb89ec1 100644
--- a/libfprint/drivers/synaptics/synaptics.c
+++ b/libfprint/drivers/synaptics/synaptics.c
@@ -36,6 +36,7 @@ static const FpIdEntry id_table[] = {
{ .vid = SYNAPTICS_VENDOR_ID, .pid = 0x00F9, },
{ .vid = SYNAPTICS_VENDOR_ID, .pid = 0x00FC, },
{ .vid = SYNAPTICS_VENDOR_ID, .pid = 0x00C2, },
+ { .vid = SYNAPTICS_VENDOR_ID, .pid = 0x00C4, },
{ .vid = SYNAPTICS_VENDOR_ID, .pid = 0x0100, },
{ .vid = SYNAPTICS_VENDOR_ID, .pid = 0x00F0, },
{ .vid = SYNAPTICS_VENDOR_ID, .pid = 0x0103, },
```
Thanks and feel free to contact if any questions.
Tom Pavel
pavel@alum.mit.eduhttps://gitlab.freedesktop.org/libfprint/libfprint/-/issues/518fprintd/data/meson.build:25:0: ERROR: Function does not take positional argum...2022-11-09T22:38:40ZLinuxTux193fprintd/data/meson.build:25:0: ERROR: Function does not take positional arguments.Hi, i'm installing the drivers using this command: `meson fprintd fprintd/_build `, and i'm having this error:
`fprintd/data/meson.build:25:0: ERROR: Function does not take positional arguments.`
The full log is [here](https://pastebin.c...Hi, i'm installing the drivers using this command: `meson fprintd fprintd/_build `, and i'm having this error:
`fprintd/data/meson.build:25:0: ERROR: Function does not take positional arguments.`
The full log is [here](https://pastebin.com/671nA8kU)
Please help mehttps://gitlab.freedesktop.org/libfprint/libfprint/-/issues/517Goodix 27c6:639c crc error2023-09-27T16:33:26ZChris LongrosGoodix 27c6:639c crc errorI currently use a Dell Inspiron 15 5510 Laptop with a Goodix fingerprint sensor.
Although it functioned perfect with the driver, when I later tried to enroll other fingers I got the following error message:
```
**Using device /net/react...I currently use a Dell Inspiron 15 5510 Laptop with a Goodix fingerprint sensor.
Although it functioned perfect with the driver, when I later tried to enroll other fingers I got the following error message:
```
**Using device /net/reactivated/Fprint/Device/0
failed to claim device: GDBus.Error:net.reactivated.Fprint.Error.Internal: Open failed with error: Package crc check failed**
```****https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/516fingerprint scanner - Bus 003 Device 003: ID 04e8:730b Samsung Electronics Co...2023-06-11T14:53:00ZJoel Webbfingerprint scanner - Bus 003 Device 003: ID 04e8:730b Samsung Electronics Co., Ltd Fingerprint Sensor Device - 730Bthe Samsung fingerprint scanner is not supported yet.
Bus 003 Device 003: ID 04e8:730b Samsung Electronics Co., Ltd Fingerprint Sensor Device - 730B
If there is a way to get it working, that would be greatthe Samsung fingerprint scanner is not supported yet.
Bus 003 Device 003: ID 04e8:730b Samsung Electronics Co., Ltd Fingerprint Sensor Device - 730B
If there is a way to get it working, that would be greathttps://gitlab.freedesktop.org/libfprint/libfprint/-/issues/515KUbuntu: Can't log in via GUI login screen after `fprintd-enroll` (neither wi...2023-09-27T17:02:56ZAts UiboupinKUbuntu: Can't log in via GUI login screen after `fprintd-enroll` (neither with fingerprint nor password)On KUbuntu (Ubuntu with KDE) this approach prevented logging in after running `fprintd-enroll` even with password!
Login screen staid "frozen" until reboot. Fingerprint worked on command line, but not on login-screen!
# Rescue solution...On KUbuntu (Ubuntu with KDE) this approach prevented logging in after running `fprintd-enroll` even with password!
Login screen staid "frozen" until reboot. Fingerprint worked on command line, but not on login-screen!
# Rescue solution that worked for me
Following steps helped me to fix logging in via login screen using password by disabling fingerprint authentication method. I hope someone falling into the same trap appreciates these instructions:
1) In login screen switch from GUI to terminal single-user mode (using `Ctrl + Alt + F3`)
2) log in with your user (there in terminal fingerprint actually worked) - after login you still can use only terminal, but not GUI!
3) edit `/etc/pam.d/common-auth` by removing line related to fingerprint:
`auth [success=2 default=ignore] pam_fprintd.so max-tries=1 timeout=10 # debug`
4) log out - now logging in with password works again
# Debug information:
My fingerprint reader is `06cb:00bd`, which is supported according to https://fprint.freedesktop.org/supported-devices.html :
`lsusb | grep -i finger`:
> Bus 005 Device 003: ID 06cb:00bd Synaptics, Inc. Prometheus MIS Touch Fingerprint Reader
`uname -a`
> Linux my-computer 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Laptop:
> Lenovo ThinkPad P14s Gen 2ahttps://gitlab.freedesktop.org/libfprint/libfprint/-/issues/514Support for ELAN7001 (04F3:3128)2023-09-27T17:05:41Zth1nhhdkSupport for ELAN7001 (04F3:3128)- on Asus Vivobook 14 A415
- Tried writing configuration, doesnt work
```
{.udev_types = ELANSPI_UDEV_TYPES, .spi_acpi_id = "ELAN7001", .hid_id = {.vid = ELANSPI_TP_VID, .pid = 0x3128}, .driver_data = ELANSPI_NO_ROTATE},
```
```
[th1nh...- on Asus Vivobook 14 A415
- Tried writing configuration, doesnt work
```
{.udev_types = ELANSPI_UDEV_TYPES, .spi_acpi_id = "ELAN7001", .hid_id = {.vid = ELANSPI_TP_VID, .pid = 0x3128}, .driver_data = ELANSPI_NO_ROTATE},
```
```
[th1nhhdk@fedora examples]$ sudo ./enroll
This program will enroll the selected finger overwriting any print for the same finger that was enrolled previously. Fingerprint updates without erasing old data are possible on devices supporting that. Ctrl+C interrupts program execution.
Choose the finger to enroll:
[0] left thumb
[1] left index
[2] left middle
[3] left ring
[4] left little
[5] right thumb
[6] right index
[7] right middle
[8] right ring
[9] right little
> 5
(process:69146): libfprint-context-DEBUG: 22:24:27.579: Initializing FpContext (libfprint version 1.94.4)
(process:69146): libfprint-context-DEBUG: 22:24:27.581: No driver found for USB device 1D6B:0003
(process:69146): libfprint-context-DEBUG: 22:24:27.581: No driver found for USB device 0BDA:0129
(process:69146): libfprint-context-DEBUG: 22:24:27.581: No driver found for USB device 0408:30D0
(process:69146): libfprint-context-DEBUG: 22:24:27.581: No driver found for USB device 8087:0026
(process:69146): libfprint-context-DEBUG: 22:24:27.581: No driver found for USB device 1D6B:0002
(process:69146): libfprint-device-DEBUG: 22:24:27.581: Device reported probe completion
(process:69146): libfprint-device-DEBUG: 22:24:27.581: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(process:69146): libfprint-device-DEBUG: 22:24:27.581: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
Selected device 0 (ElanTech Embedded Fingerprint Sensor) claimed by elanspi driver
(process:69146): libfprint-elanspi-DEBUG: 22:24:27.582: 8740010544: ../libfprint/drivers/elanspi.c:1562
(process:69146): libfprint-image_device-DEBUG: 22:24:27.582: Image device open completed
(process:69146): libfprint-device-DEBUG: 22:24:27.582: Device reported open completion
(process:69146): libfprint-device-DEBUG: 22:24:27.582: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(process:69146): libfprint-device-DEBUG: 22:24:27.582: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
Opened device.
The device supports fingerprint updates.
Should an existing fingerprint be updated instead of being replaced (if present)? Enter Y/y or N/n to make a choice.
(process:69146): libfprint-WARNING **: 22:24:28.818: Invalid choice
, should be Y/y or N/n.
It's now time to enroll your finger.
You will need to successfully scan your right thumb finger 7 times to complete the process.
Scan your finger now.
(process:69146): libfprint-WARNING **: 22:24:28.818: Error loading storage, assuming it is empty
(process:69146): libfprint-device-DEBUG: 22:24:28.819: Updated temperature model after 1.24 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:69146): libfprint-image_device-DEBUG: 22:24:28.819: Activating image device
(process:69146): libfprint-image_device-DEBUG: 22:24:28.819: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:69146): libfprint-SSM-DEBUG: 22:24:28.819: [elanspi] ELANSPI_INIT_NSTATES entering state 0
(process:69146): libfprint-device-DEBUG: 22:24:28.819: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:69146): libfprint-SSM-DEBUG: 22:24:28.819: [elanspi] ELANSPI_INIT_NSTATES entering state 1
(process:69146): libfprint-elanspi-DEBUG: 22:24:28.819: <init> got status 41
(process:69146): libfprint-elanspi-DEBUG: 22:24:28.820: <init> sync hw reset
(process:69146): libfprint-SSM-DEBUG: 22:24:28.820: [elanspi] ELANSPI_INIT_NSTATES entering state 2
(process:69146): libfprint-SSM-DEBUG: 22:24:28.824: [elanspi] ELANSPI_INIT_NSTATES entering state 3
(process:69146): libfprint-elanspi-DEBUG: 22:24:28.824: <init> sw reset ok
(process:69146): libfprint-SSM-DEBUG: 22:24:28.825: [elanspi] ELANSPI_INIT_NSTATES entering state 4
(process:69146): libfprint-elanspi-DEBUG: 22:24:28.825: <init> raw height = 80
(process:69146): libfprint-SSM-DEBUG: 22:24:28.825: [elanspi] ELANSPI_INIT_NSTATES entering state 5
(process:69146): libfprint-elanspi-DEBUG: 22:24:28.825: <init> raw width = 80
(process:69146): libfprint-SSM-DEBUG: 22:24:28.825: [elanspi] ELANSPI_INIT_NSTATES entering state 6
(process:69146): libfprint-elanspi-DEBUG: 22:24:28.825: <init> raw reg17 = 100
(process:69146): libfprint-SSM-DEBUG: 22:24:28.825: [elanspi] ELANSPI_INIT_NSTATES entering state 7
(process:69146): libfprint-elanspi-DEBUG: 22:24:28.825: <init> raw version = 27
(process:69146): libfprint-elanspi-DEBUG: 22:24:28.825: <init/detect> after hardcoded lookup; 80x80, version 2
(process:69146): libfprint-elanspi-DEBUG: 22:24:28.825: <init/detect> found sensor ID 14 => [eFSA80SC] (80 x 80)
(process:69146): libfprint-SSM-DEBUG: 22:24:28.826: [elanspi] ELANSPI_INIT_NSTATES entering state 8
(process:69146): libfprint-SSM-DEBUG: 22:24:28.830: [elanspi] ELANSPI_INIT_NSTATES entering state 9
(process:69146): libfprint-SSM-DEBUG: 22:24:28.830: [elanspi] ELANSPI_INIT_NSTATES entering state 19
(process:69146): libfprint-elanspi-DEBUG: 22:24:28.830: <init/calibrate> starting calibrate
(process:69146): libfprint-SSM-DEBUG: 22:24:28.830: [elanspi] HV calibrate entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.831: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.831: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.831: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.831: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.831: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.831: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.831: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.832: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.832: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.832: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.832: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.832: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.832: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.832: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.832: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.832: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.832: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.833: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.834: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.835: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.835: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.835: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.835: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.835: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.835: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.835: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.835: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.835: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.835: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.835: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.835: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.836: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.837: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.838: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES completed successfully
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.839: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.840: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.841: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.842: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.843: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.844: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.844: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.844: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.844: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.844: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.844: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.844: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.844: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.844: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.844: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.844: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.844: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.844: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.845: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.846: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.847: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1
(process:69146): libfprint-SSM-DEBUG: 22:24:28.848: [elanspi] ELANSPI_WRTABLE_NSTATES completed successfully
(process:69146): libfprint-SSM-DEBUG: 22:24:28.849: [elanspi] ELANSPI_CAPTHV_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.864: [elanspi] ELANSPI_CAPTHV_NSTATES completed successfully
(process:69146): libfprint-SSM-DEBUG: 22:24:28.864: [elanspi] ELANSPI_CAPTHV_NSTATES entering state 0
(process:69146): libfprint-SSM-DEBUG: 22:24:28.914: [elanspi] SSM ELANSPI_CAPTHV_NSTATES failed in state 2 with error: timed out waiting for image
(process:69146): libfprint-SSM-DEBUG: 22:24:28.914: [elanspi] ELANSPI_CAPTHV_NSTATES completed with error: timed out waiting for image
(process:69146): libfprint-SSM-DEBUG: 22:24:28.914: [elanspi] SSM HV calibrate failed in state 9 with error: timed out waiting for image
(process:69146): libfprint-SSM-DEBUG: 22:24:28.914: [elanspi] HV calibrate entering state 13
(process:69146): libfprint-elanspi-DEBUG: 22:24:28.914: <calibhv> calibration ok, saving bg image
(process:69146): libfprint-SSM-DEBUG: 22:24:28.914: [elanspi] HV calibrate completed with error: timed out waiting for image
(process:69146): libfprint-SSM-DEBUG: 22:24:28.914: [elanspi] SSM ELANSPI_INIT_NSTATES failed in state 19 with error: timed out waiting for image
(process:69146): libfprint-SSM-DEBUG: 22:24:28.914: [elanspi] ELANSPI_INIT_NSTATES completed with error: timed out waiting for image
(process:69146): libfprint-elanspi-DEBUG: 22:24:28.914: 8741343310: ../libfprint/drivers/elanspi.c:1596
(process:69146): libfprint-image_device-DEBUG: 22:24:28.914: Image device activation failed
(process:69146): libfprint-device-DEBUG: 22:24:28.914: Device reported generic error (timed out waiting for image) during action; action was: FPI_DEVICE_ACTION_ENROLL
(process:69146): libfprint-device-DEBUG: 22:24:28.914: Device reported enroll completion
(process:69146): libfprint-device-DEBUG: 22:24:28.914: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
(process:69146): libfprint-device-DEBUG: 22:24:28.914: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(process:69146): libfprint-WARNING **: 22:24:28.914: Enroll failed with error timed out waiting for image
(process:69146): libfprint-image_device-DEBUG: 22:24:28.914: Image device close completed
(process:69146): libfprint-device-DEBUG: 22:24:28.914: Device reported close completion
(process:69146): libfprint-device-DEBUG: 22:24:28.914: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
(process:69146): libfprint-device-DEBUG: 22:24:28.914: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
```https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/512fpcmoc: Ensure the current SSM is never overwritten2022-10-28T08:16:20ZMarco Trevisanfpcmoc: Ensure the current SSM is never overwrittenBasically implies restoring (and fixing the suspend/resume case) for:
```diff
diff --git a/libfprint/drivers/fpcmoc/fpc.c b/libfprint/drivers/fpcmoc/fpc.c
index 56adfab7..b64cc36e 100644
--- a/libfprint/drivers/fpcmoc/fpc.c
+++ b/libfpr...Basically implies restoring (and fixing the suspend/resume case) for:
```diff
diff --git a/libfprint/drivers/fpcmoc/fpc.c b/libfprint/drivers/fpcmoc/fpc.c
index 56adfab7..b64cc36e 100644
--- a/libfprint/drivers/fpcmoc/fpc.c
+++ b/libfprint/drivers/fpcmoc/fpc.c
@@ -248,7 +248,7 @@ fpc_send_ctrl_cmd (FpDevice *dev)
cmd_data->index,
cmd_data->data_len);
- transfer->ssm = g_steal_pointer (&self->cmd_ssm);
+ transfer->ssm = self->cmd_ssm;
if (cmdtype != FPC_CMDTYPE_FROM_DEVICE &&
cmd_data->data != NULL &&
cmd_data->data_len != 0)
@@ -345,8 +345,6 @@ fpc_sensor_cmd (FpiDeviceFpcMoc *self,
g_return_if_fail (cmd_data);
g_return_if_fail (cmd_data->cmdtype != FPC_CMDTYPE_UNKNOWN);
- g_assert (self->cmd_ssm == NULL);
-
data = g_memdup2 (cmd_data, sizeof (CommandData));
if (wait_data_delay)
```https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/510Support for 04f3:0c77 Elan Microelectronics Corp. ELAN:ARM-M42023-09-27T17:05:40ZstarsforeveryoneSupport for 04f3:0c77 Elan Microelectronics Corp. ELAN:ARM-M4Hello dear developers!
I've been trying to add support for my ELAN Fingerprint sensor 04f3:0c77 by trying the following steps:
1. Add device to libfprint/drivers/elan.h
`{.vid = ELAN_VEND_ID, .pid = 0x0c77, .driver_data = ELAN_ALL_DEV...Hello dear developers!
I've been trying to add support for my ELAN Fingerprint sensor 04f3:0c77 by trying the following steps:
1. Add device to libfprint/drivers/elan.h
`{.vid = ELAN_VEND_ID, .pid = 0x0c77, .driver_data = ELAN_ALL_DEV},`
2. Recompile with meson
`meson builddir && meson compile -C builddir`
3. Try img-capture with sudo
`cd builddir/examples && sudo ./img-capture`
Sadly, I cannot get img-capture to actually capture an image.
If I swipe my finger (or do nothing), the device just times out:
`(process:32273): libfprint-WARNING **: 13:06:44.353: Error capturing data: The swipe was too short, please try again.`
Interestingly, if I put my finger onto the reader (no swiping) _before_ starting the img-capture command and _leave_ it there, the device throws a different error message:
`(process:32208): libfprint-WARNING **: 13:06:04.334: Error capturing data: device sent more data than requested`
This tells me that the device must be initialized properly and must be able to "see" my finger somehow. So, I have hopes to perhaps get it working?
It would be very nice if some of you smart guys could give me a hint as to how to proceed further.
I've been doing finger acrobatics and tried all well-known 2048 different versions of the famous _Olympic finger swiping discipline_ with no success.
Kind regards
LOGFILES:
No finger: [finger_off.txt](/uploads/f22b82cf3bf1b3504984ef033de5d0a2/finger_off.txt)
Finger left static on before starting img-capture: [finger_on.txt](/uploads/2021623a29251aafb5f5747b5f2f5567/finger_on.txt)
Finger doing dynamic swipe while running img-capture: [finger_swipe.txt](/uploads/54d07f8919c2c6524dbb877fd615b85b/finger_swipe.txt)https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/509Support for CanvasBio CB20002024-03-03T23:47:15ZStandingPadSupport for CanvasBio CB2000I noticed on my Galaxy Book2 360 (I'm currently using Fedora 36 with the most recent updates) that it appears when using `lsusb` as the following:
```
Bus 003 Device 003: ID 2df0:0003 Generic CanvasBio CB2000
```
And looking u CanvasBio ...I noticed on my Galaxy Book2 360 (I'm currently using Fedora 36 with the most recent updates) that it appears when using `lsusb` as the following:
```
Bus 003 Device 003: ID 2df0:0003 Generic CanvasBio CB2000
```
And looking u CanvasBio it's clear that it's the fingerprint scanner that Samsung uses. I'm not sure if there's a Linux driver available for it, but Linux does recognize it