[TRACKING] Fingerprint reader failing to register on 13th gen

+1 That installing windows first made the fingerprint reader “just work”.

OOTB I installed nixOS and couldn’t get the fingerprint reader working. I decided to dual boot and (1) erased the drive, (2) created an empty NTFS partition for windows, (3) created windows install media from another windows machine, direct ISO didn’t work, (4) installed windows, (5) installed nixos on the rest of the drive also creating a separate /boot partition during the nixos installer.

1 Like

There is an update for Windows that provides a arguably method for folks. While we wait to get this on LVFS, this is absolutely a method that does work.

Alright, here is updated guidance.

Please note the header of the file- if you are not wanting to take this approach or it errors out, please wait for the LVFS update.

For earlier beta testers, this is a new cab file - if it failed for you previously:

  • Check sudo cat /usr/share/fwupd/quirks.d/goodixmoc.quirk and make sure both entries are present and there is no duplication.

  • Try the updated instructions linked above.

6 Likes

I followed the instructions as described and my fingerprint reader is now recognized. That said, I’ve successfully added my fingerprint multiple times, but using fprintd-verify and logging in with the same finger has never succeeded.

I’m enrolling it via Fedora 38 w/ Gnome in Settings. Could I be enrolling it incorrectly?

doas fwupdtool install --allow-reinstall --allow-older goodix-moc-609c-v01000330.cab
Writing…                 [*************************************  ]22:00:54.752 FuEngine             failed to update-cleanup after failed update: failed to get device before update cleanup: failed to wait for device: device <foo> did not come back

failed to write: failed to reply: transfer timed out

It seemed to work second try though, went from

Current version:    01000320

to

        New version:      01000330
doas fprintd-enroll hugh
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-remove-and-retry
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-retry-scan
Enroll result: enroll-stage-passed
Enroll result: enroll-completed
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.44, NixOS, 23.11 (Tapir), 23.11.20230813.100a155`

I would try this, as sudo. Make sure to make it executable. Reboot, re-register again, reboot, then try again to login. Note, it’s not unheard of for the fingerprint reader (my phone, any laptop I own does this to me) to misbehave and fail to see my fingerprint. So it may be “fine”, but let’s try this first.

1 Like

This looks good based on this: https://github.com/FrameworkComputer/linux-docs/blob/main/13th-gen-fingerprint-reader-firmware.md#download-this-cab-to-your-home-directory-path

Continuing the discussion from [TRACKING] Fingerprint reader failing to register on 13th gen:

This was it - thank you!

2 Likes

After a long day, this simple statement made my evening! Thank you! :raised_hands: :slight_smile:

3 Likes

Instructions above worked for me! Didn’t need to do anything more than the steps that @Matt_Hartley posted from the 13th-gen-fingerprint-reader-firmware.md file. Many thanks!

Edit: For context: I’m running Ubuntu 22.04 LTS on the Framework 13th gen (DIY), no prior updates to the firmware and never ran Windows before. Also was able to setup sudo fingerprint authentication with no issues as well.

1 Like

@Matt_Hartley thank you, this worked for me and I now have a working fingerprint sensor! :raised_hands:

I’m on Ubuntu 22.04 and needed to add the quirk. After doing that, rebooting, and installing the updated firmware, I got the transfer error at the end of installation. At that point sudo fwupdtool get-devices --plugins goodixmoc showed no devices detected again, but sudo fwupdtool get-history did show the correct version and enabling fingerprint login then worked for the first time. After another reboot sudo fwupdtool get-devices --plugins goodixmoc is now detecting the device and showing the correct version.

1 Like

@Matt_Hartley Thanks, this worked for me too! I had the same issue as High_O_Brien though - first time failed with the same error. Immediately following that, get-devices failed:

$ sudo fwupdtool get-devices --plugins goodixmoc
Loading…                 [**********                             ]11:46:19.825 FuEngine             failed to add device usb:01:00:09: failed to get firmware version: failed to reply: device was disconnected
Loading…                 [************************************** ]
No detected device

and following attempts simply indicated that the device wasn’t connected:

$ sudo fwupdtool get-devices --plugins goodixmoc
Loading…                 [************************************** ]
No detected devices

Running install a second time worked, and then get-devices started showing the updated version.

The fingerprint settings immediately appeared in KDE/Plasma’s User settings, and I could enroll a fingerprint. Now if only SDDM supported it! :grin:

1 Like

Thank you so much, had to run the install twice but after that it worked perfectly!

2 Likes

I installed the cab file and the fingerprint reader was detected. When i tried to register a fingerprint I do not see the image of the fingerprint and when I place my fingerprint on the sensor, it does not register even after several minutes. I am on Fedora 38.

Thanks.

To better spot why it worked for you and not someone else, can you share your distro/version?

Let’s try this instead as it is far more verbose and will give me a better idea why it failed. The screen you’ve shared looks like it just wants to try reading again (normal).

In a terminal:

fprintd-enroll

The paste the entire output back here please.

When trying to register a fingerprint from the commandline I get:
(base) [shsnyder@fedora ~]$ fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed

It stays at this output indefinitely (I stopped waiting after a minute or so). If I take my finger off the sensor it senses that and returns

Enroll result: enroll-retry-scan

This is the same behavior as I see when using the Gnome widget.

I will try some more variations.

Thanks.

I googled around and found how to enable DEBUG for fprintd (see [fprintd] debug 'fprintd-enroll' and 'fprintd-verify' (#4) · Issues · chester / libfprint · GitLab ).
In one terminal I had "sudo env G_MESSAGES_DEBUG=all /usr/libexec/fprintd -t " and in the other I ran sudo fprintd-enroll.
You can see the initialization, the iniital recognition of something on the sensor, and then no entry for close to 2 minutes. The log started again when I took my finger off the sensor.
Here is the DEBUG log info:

(base) [shsnyder@fedora ~]$ sudo env G_MESSAGES_DEBUG=all /usr/libexec/fprintd -t 
(fprintd:11730): GLib-GIO-DEBUG: 21:23:43.975: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
(fprintd:11730): fprintd-DEBUG: 21:23:43.976: About to load configuration file '/etc/fprintd.conf'
(fprintd:11730): fprintd-DEBUG: 21:23:43.976: Launching FprintObject
(fprintd:11730): libfprint-context-DEBUG: 21:23:43.977: Initializing FpContext (libfprint version 1.94.4)
(fprintd:11730): fprintd-DEBUG: 21:23:43.985: Preparing devices for resume
(fprintd:11730): libfprint-context-DEBUG: 21:23:43.986: No driver found for USB device 1D6B:0003
(fprintd:11730): libfprint-context-DEBUG: 21:23:43.986: No driver found for USB device 0BDA:5634
(fprintd:11730): libfprint-context-DEBUG: 21:23:43.986: No driver found for USB device 32AC:0002
(fprintd:11730): libfprint-context-DEBUG: 21:23:43.986: No driver found for USB device 8087:0032
(fprintd:11730): libfprint-context-DEBUG: 21:23:43.986: No driver found for USB device 1D6B:0002
(fprintd:11730): libfprint-context-DEBUG: 21:23:43.986: No driver found for USB device 1D6B:0003
(fprintd:11730): libfprint-context-DEBUG: 21:23:43.986: No driver found for USB device 1D6B:0002
(fprintd:11730): libfprint-device-DEBUG: 21:23:44.329: Device reported probe completion
(fprintd:11730): fprintd-DEBUG: 21:23:44.329: Got delay inhibitor for sleep.
(fprintd:11730): libfprint-device-DEBUG: 21:23:44.329: Completing action FPI_DEVICE_ACTION_PROBE in idle!
(fprintd:11730): libfprint-device-DEBUG: 21:23:44.329: Not updating temperature model, device can run continuously!
libusb: error [udev_hotplug_event] ignoring udev action change
(fprintd:11730): fprintd-DEBUG: 21:23:44.335: Device Goodix MOC Fingerprint Sensor scan type changed to 'press'
(fprintd:11730): fprintd-DEBUG: 21:23:44.335: Device Goodix MOC Fingerprint Sensor enroll stages changed to 13
(fprintd:11730): fprintd-DEBUG: 21:23:44.335: Finger present 0
(fprintd:11730): fprintd-DEBUG: 21:23:44.335: Finger needed 0
(fprintd:11730): fprintd-DEBUG: 21:23:44.335: entering main loop
(fprintd:11730): fprintd-DEBUG: 21:23:44.336: D-Bus service launched with name: net.reactivated.Fprint
libusb: error [udev_hotplug_event] ignoring udev action change
(fprintd:11730): fprintd-DEBUG: 21:24:15.343: Requesting authorization from :1.297 to call method 'ListEnrolledFingers' for device 'Goodix MOC Fingerprint Sensor'
(fprintd:11730): fprintd-DEBUG: 21:24:15.344: Getting authorization to perform Polkit action net.reactivated.fprint.device.setusername
(fprintd:11730): fprintd-DEBUG: 21:24:15.346: Getting authorization to perform Polkit action net.reactivated.fprint.device.verify
(fprintd:11730): fprintd-DEBUG: 21:24:15.348: Authorization granted to :1.297 to call method 'ListEnrolledFingers' for device 'Goodix MOC Fingerprint Sensor'!
(fprintd:11730): fprintd-DEBUG: 21:24:15.348: file_storage_discover_prints() for user 'shsnyder' in '/var/lib/fprint/shsnyder/goodixmoc/UIDEBE47CD1_XXXX_MOC_B0'
(fprintd:11730): fprintd-DEBUG: 21:24:15.348: scan_dev_storedir(): opendir("/var/lib/fprint/shsnyder/goodixmoc/UIDEBE47CD1_XXXX_MOC_B0") failed: Error opening directory “/var/lib/fprint/shsnyder/goodixmoc/UIDEBE47CD1_XXXX_MOC_B0”: No such file or directory
(fprintd:11730): GLib-GIO-DEBUG: 21:24:15.348: GTask [gio] D-Bus interface method dispatch (source object: 0x561d73cc86b0, source tag: 0x7fc8947fd350) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:11730): fprintd-DEBUG: 21:24:26.803: Requesting authorization from :1.299 to call method 'Claim' for device 'Goodix MOC Fingerprint Sensor'
(fprintd:11730): fprintd-DEBUG: 21:24:26.804: Getting authorization to perform Polkit action net.reactivated.fprint.device.verify
(fprintd:11730): fprintd-DEBUG: 21:24:26.808: Authorization granted to :1.299 to call method 'Claim' for device 'Goodix MOC Fingerprint Sensor'!
(fprintd:11730): fprintd-DEBUG: 21:24:26.808: user 'root' claiming the device: 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.147: [goodixmoc] FP_INIT_NUM_STATES entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.147: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): GLib-GIO-DEBUG: 21:24:27.147: GTask [gio] D-Bus interface method dispatch (source object: 0x561d73cc86b0, source tag: 0x7fc8947fd350) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.148: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.148: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.149: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.152: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-goodixmoc-DEBUG: 21:24:27.153: Firmware type: APP
(fprintd:11730): libfprint-goodixmoc-DEBUG: 21:24:27.153: Firmware version: 01000330
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.153: [goodixmoc] FP_INIT_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.153: [goodixmoc] FP_CMD_NUM_STATES entering state 0
libusb: error [udev_hotplug_event] ignoring udev action change
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.153: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.154: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.154: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.155: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.155: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.155: [goodixmoc] FP_INIT_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.155: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.156: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.156: [goodixmoc] FP_CMD_NUM_STATES entering state 1
libusb: error [udev_hotplug_event] ignoring udev action change
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.157: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.157: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.160: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.161: [goodixmoc] FP_INIT_NUM_STATES completed successfully
(fprintd:11730): libfprint-device-DEBUG: 21:24:27.161: Device reported open completion
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.161: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-device-DEBUG: 21:24:27.161: Completing action FPI_DEVICE_ACTION_OPEN in idle!
(fprintd:11730): libfprint-device-DEBUG: 21:24:27.161: Not updating temperature model, device can run continuously!
(fprintd:11730): fprintd-DEBUG: 21:24:27.161: claimed device 0
(fprintd:11730): fprintd-DEBUG: 21:24:27.163: Requesting authorization from :1.299 to call method 'EnrollStart' for device 'Goodix MOC Fingerprint Sensor'
(fprintd:11730): fprintd-DEBUG: 21:24:27.163: Getting authorization to perform Polkit action net.reactivated.fprint.device.enroll
(fprintd:11730): fprintd-DEBUG: 21:24:27.168: Authorization granted to :1.299 to call method 'EnrollStart' for device 'Goodix MOC Fingerprint Sensor'!
(fprintd:11730): fprintd-DEBUG: 21:24:27.168: file_storage_print_data_load(): loaded '/var/lib/fprint/root/goodixmoc/UIDEBE47CD1_XXXX_MOC_B0/7' Unknown error -2
(fprintd:11730): fprintd-DEBUG: 21:24:27.169: start enrollment device 0 finger 7
(fprintd:11730): libfprint-device-DEBUG: 21:24:27.169: Not updating temperature model, device can run continuously!
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.169: [goodixmoc] verify entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.169: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): GLib-GIO-DEBUG: 21:24:27.169: GTask [gio] D-Bus interface method dispatch (source object: 0x561d73cc86b0, source tag: 0x7fc8947fd350) finalized without ever returning (using g_task_return_*()). This potentially indicates a bug in the program.
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.169: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.170: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.170: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.170: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-DEBUG: 21:24:27.171: Power button shield feature not supported!

(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.171: [goodixmoc] verify entering state 1
(fprintd:11730): libfprint-device-DEBUG: 21:24:27.171: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(fprintd:11730): fprintd-DEBUG: 21:24:27.171: Finger present 0
(fprintd:11730): fprintd-DEBUG: 21:24:27.171: Finger needed 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.171: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.171: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.171: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.172: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:27.172: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.780: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-device-DEBUG: 21:24:31.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(fprintd:11730): fprintd-DEBUG: 21:24:31.781: Finger present 1
(fprintd:11730): fprintd-DEBUG: 21:24:31.781: Finger needed 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.781: [goodixmoc] verify entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.781: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.781: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.781: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.782: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.782: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.784: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-device-DEBUG: 21:24:31.784: Device reported identify result
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.784: [goodixmoc] verify entering state 3
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.784: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.784: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.785: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.785: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.786: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.786: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-DEBUG: 21:24:31.786: Power button shield feature not supported!

(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.786: [goodixmoc] verify completed successfully
(fprintd:11730): libfprint-goodixmoc-DEBUG: 21:24:31.786: Verify complete!
(fprintd:11730): libfprint-device-DEBUG: 21:24:31.787: Device reported identify completion
(fprintd:11730): libfprint-device-DEBUG: 21:24:31.787: Device reported finger status change: FP_FINGER_STATUS_NONE
(fprintd:11730): fprintd-DEBUG: 21:24:31.787: Finger present 0
(fprintd:11730): fprintd-DEBUG: 21:24:31.787: Finger needed 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.787: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-device-DEBUG: 21:24:31.787: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
(fprintd:11730): libfprint-device-DEBUG: 21:24:31.787: Not updating temperature model, device can run continuously!
(fprintd:11730): libfprint-device-DEBUG: 21:24:31.789: Not updating temperature model, device can run continuously!
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.789: [goodixmoc] enroll entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.789: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.789: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.790: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.790: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.791: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-DEBUG: 21:24:31.791: Power button shield feature not supported!

(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.791: [goodixmoc] enroll entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.791: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.791: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.792: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.792: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.793: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.796: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.796: [goodixmoc] enroll entering state 4
(fprintd:11730): libfprint-device-DEBUG: 21:24:31.796: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(fprintd:11730): fprintd-DEBUG: 21:24:31.796: Finger present 0
(fprintd:11730): fprintd-DEBUG: 21:24:31.796: Finger needed 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.796: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.797: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.797: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.797: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:31.798: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.048: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-device-DEBUG: 21:24:32.048: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
(fprintd:11730): fprintd-DEBUG: 21:24:32.048: Finger present 1
(fprintd:11730): fprintd-DEBUG: 21:24:32.049: Finger needed 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.049: [goodixmoc] enroll entering state 5
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.049: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.049: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.049: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.050: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.051: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.113: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-device-DEBUG: 21:24:32.113: Device reported enroll progress, reported 1 of 12 have been completed
(fprintd:11730): fprintd-DEBUG: 21:24:32.113: enroll_stage_cb: result enroll-stage-passed
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.113: [goodixmoc] enroll entering state 6
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.113: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.114: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.114: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.115: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:32.116: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.331: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.332: [goodixmoc] enroll entering state 6
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.332: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.332: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.332: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.334: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.335: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.369: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-device-DEBUG: 21:24:37.370: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(fprintd:11730): fprintd-DEBUG: 21:24:37.370: Finger present 0
(fprintd:11730): fprintd-DEBUG: 21:24:37.370: Finger needed 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.370: [goodixmoc] enroll entering state 4
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.370: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.370: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.370: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.372: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:24:37.372: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-SSM-DEBUG: 21:26:24.328: [goodixmoc] FP_CMD_NUM_STATES entering state 2
(fprintd:11730): libfprint-goodixmoc-DEBUG: 21:26:24.329: Capture sample failed, result: 0xc0
(fprintd:11730): libfprint-device-DEBUG: 21:26:24.329: Device reported enroll progress, reported 1 of 12 have been completed
(fprintd:11730): fprintd-DEBUG: 21:26:24.329: enroll_stage_cb: result enroll-retry-scan
(fprintd:11730): libfprint-SSM-DEBUG: 21:26:24.329: [goodixmoc] enroll entering state 4
(fprintd:11730): libfprint-SSM-DEBUG: 21:26:24.329: [goodixmoc] FP_CMD_NUM_STATES entering state 0
(fprintd:11730): libfprint-SSM-DEBUG: 21:26:24.329: [goodixmoc] FP_CMD_NUM_STATES completed successfully
(fprintd:11730): libfprint-SSM-DEBUG: 21:26:24.330: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:26:24.331: [goodixmoc] FP_CMD_NUM_STATES entering state 1
(fprintd:11730): libfprint-SSM-DEBUG: 21:26:24.331: [goodixmoc] FP_CMD_NUM_STATES entering state 2

Please let me know if there is any other information that I can provide.

–Scott

Just received a 13th gen input cover to fix a keyboard issue and had to perform this fix. The guide at https://github.com/FrameworkComputer/linux-docs/blob/main/13th-gen-fingerprint-reader-firmware.md worked successfully.

I do still have a Windows dual boot so technically I could have done this the easy way, but a manual fwupd was quicker.

1 Like

Of course: Ubuntu 23.04 x86_64 (6.2.0-27-generic)