Halt after 1-st scan

[AMV007]

right now fingerprint GUI halt, trying to take second scan of the same finger with this device. ID 1c7a:0603 LighTuning Technology Inc.

[patrickmarlier]

Could you please give more details on what instruction it is blocked? (debug) Also I don't own this device anymore so I will just try to remember how this was working.

[cih997]

Same issue here. What I've noticed is that permissions issue:

colord-sane: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
colord-sane: message repeated 3 times: [ io/hpmud/musb.c 2101: Invalid usb_open: Permission denied]
colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1

Updating persmissions via sudo chmod a+rw /dev/bus/usb/00X/00Y does not help. Same issue after creating /etc/udev/rules.d/90-egis.rules file.

When doing scan it looks like the device is being disconnected:

upowerd[3673]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-4/1-4:1.0
kernel: [  450.043496] usb 1-4: USB disconnect, device number 8
upowerd[3673]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-4/1-4:1.0
upowerd[3673]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-4

And then immediately connected again with new device number:

kernel: [  450.385784] usb 1-4: new full-speed USB device number 9 using xhci_hcd
kernel: [  450.701880] usb 1-4: New USB device found, idVendor=1c7a, idProduct=0603
kernel: [  450.701883] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: [  450.701885] usb 1-4: Product: EgisTec_ES603
kernel: [  450.701887] usb 1-4: Manufacturer: EgisTec
mtp-probe: checking bus 1, device 9: "/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-4"
mtp-probe: bus: 1, device: 9 was not an MTP device
upowerd[3673]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-4
colord-sane: io/hpmud/musb.c 2101: Invalid usb_open: Permission denied
colord-sane: message repeated 3 times: [ io/hpmud/musb.c 2101: Invalid usb_open: Permission denied]
colord-sane: io/hpmud/pp.c 627: unable to read device-id ret=-1

@patrickmarlier let me know if you need any other debug info.

[patrickmarlier]

"colord-sane" is another process trying to access the device and it seems indeed that the permissions are not right. So probably the udev rules is not matching something and the permissions are not changed.

Since you were able to do a scan, it seems that at least you managed to fix the permissions. Could you send the debug logs of the driver when you did the scan? So we can see the last frame sent to the device. I am also wondering if upowerd or colord-sane could create an issue trying to talk with the device.

[cih997]

Thanks @patrickmarlier.

I think that permission denied error is not related or at least does not break the scanner. I used fprintd-enroll instead of fingerprint gui and added successfully my fingers.

However, when loggin in or confirming sudo commands, finger detection works once per 20-30 tries. No idea why is that, the enroll process works without any issues but then the detection via system or fprintd-verify works rarely only.

[patrickmarlier]

About the efficiency on the finger detection, what could help is if you can get the pictures when you enroll (to check the quality) and if you can check the number of minutiae detected. You can also use fprint-demo to check if it works well.

[cih997]

@patrickmarlier thanks. I upgraded fprintd related libraries manually and checked with fprint_demo how to slide my finger to get best results. That made fingerprint useful at last.

[richardnpaul]

Hmm, and now another person comes in saying that this is still an issue. I can't remember where I saw it but there was a post in a bugzilla somewhere about this sensor (which hasn't worked under Ubuntu since I got the laptop over 6 years ago) whilst I was running 19.10 and I saw that the next version might at least mitigate some issues with the Gnome app crashing as a result of issues with this sensor; which does seem to be the case.

So, I can read the fingerprint once with the gui and then it doesn't read anymore. Grepping the syslog for fprintd returns lines like this:

Jun 1 17:44:02 richard-P15SM dbus-daemon[1496]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.88' (uid=1000 pid=2664 comm="/usr/bin/gnome-shell " label="unconfined") Jun 1 17:45:16 richard-P15SM fprintd[21955]: unexpected answer CMD_20 from device(05 FF FF) Jun 1 17:45:16 richard-P15SM fprintd[21955]: unexpected answer for CMD_25 (FF) Jun 1 17:45:21 richard-P15SM fprintd[21955]: fpi_image_device_image_captured: assertion 'priv->state == FPI_IMAGE_DEVICE_STATE_CAPTURE' failed Jun 1 17:45:21 richard-P15SM fprintd[21955]: ERROR : block_offsets : image must be at least 8 by 8 in size Jun 1 17:45:21 richard-P15SM fprintd[21955]: get minutiae failed, code -80 Jun 1 17:45:21 richard-P15SM systemd[1]: fprintd.service: Main process exited, code=dumped, status=11/SEGV Jun 1 17:45:21 richard-P15SM systemd[1]: fprintd.service: Failed with result 'core-dump'. Jun 1 17:46:49 richard-P15SM dbus-daemon[1496]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.211' (uid=1000 pid=28617 comm="gnome-control-center user-accounts " label="unconfined") Jun 1 17:46:56 richard-P15SM fprintd[32892]: unexpected answer CMD_20 from device(05 FF FF) Jun 1 17:46:56 richard-P15SM fprintd[32892]: unexpected answer for CMD_25 (FF) Jun 1 17:47:02 richard-P15SM fprintd[32892]: fpi_device_enroll_progress: assertion 'error == NULL || error->domain == FP_DEVICE_RETRY' failed Jun 1 17:47:03 richard-P15SM fprintd[32892]: fpi_image_device_image_captured: assertion 'priv->state == FPI_IMAGE_DEVICE_STATE_CAPTURE' failed Jun 1 17:47:03 richard-P15SM fprintd[32892]: fpi_image_device_image_captured: assertion 'priv->state == FPI_IMAGE_DEVICE_STATE_CAPTURE' failed Jun 1 17:47:04 richard-P15SM fprintd[32892]: ERROR : block_offsets : image must be at least 8 by 8 in size Jun 1 17:47:04 richard-P15SM fprintd[32892]: get minutiae failed, code -80 Jun 1 17:47:04 richard-P15SM systemd[1]: fprintd.service: Main process exited, code=dumped, status=11/SEGV Jun 1 17:47:04 richard-P15SM systemd[1]: fprintd.service: Failed with result 'core-dump'. Jun 1 17:47:46 richard-P15SM dbus-daemon[1496]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.211' (uid=1000 pid=28617 comm="gnome-control-center user-accounts " label="unconfined") Jun 1 17:50:42 richard-P15SM systemd[1]: fprintd.service: Succeeded.

It sounds like it's going to be a struggle though, I don't have the programming set in your area and have the device, you have the skill-set but no device :/