[RESPONDED] Gnome Software Fingerprint Sensor Error Message After Every Update

After successfully updating all available firmware recently using LVFS (fwupdmgr ...), every time Gnome Software is done installing a software update, it shows an error message about the Fingerprint sensor on system reboot stating “Device cannot be used during update”. Everything on my computer works, including the Fingerprint sensor, but this is an annoyance I’d like to get rid of.

Error Snapshot

I’m on the latest firmware:

ehsanj@fw13 : ~
[0] % sudo dmidecode -t bios        
# dmidecode 3.5
Getting SMBIOS data from sysfs.
SMBIOS 3.6.0 present.
# SMBIOS implementations newer than version 3.5.0 are not
# fully supported by this version of dmidecode.

Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
	Vendor: INSYDE Corp.
	Version: 03.05
	Release Date: 03/29/2024
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 32 MB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		8042 keyboard services are supported (int 9h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 3.5
---snip---

Here’s the Fingerprint sensor info obtained via fwupdmgr get-devices:

---snip---
├─Fingerprint Sensor:
│     Device ID:          23ec719b6aabc2d2dac5176c232f0da7a21881b0
│     Summary:            Match-On-Chip fingerprint sensor
│     Current version:    01000334
│     Vendor:             Goodix (USB:0x27C6)
│     Install Duration:   10 seconds
│     Serial Number:      UIDDE76F500_XXXX_MOC_B0
│     GUID:               1e8c8470-a49c-571a-82fd-19c9fa32b8c3 ← USB\VID_27C6&PID_609C
│     Device Flags:       • Updatable
│                         • Device stages updates
│                         • Device can recover flash failures
│                         • Signed Payload
---snip---

Finally, here’s my system info:

Framework Laptop 13 #framework-laptop:diy-edition Linux linux help

Let’s get out of the GUI so we can get a better picture of what is happening. Per our docs, we always recommend using CLI for firmware management as the GUI is not great for details.

What is the output of the following:

fwupdmgr get-devices 1e8c8470-a49c-571a-82fd-19c9fa32b8c3

fwupdmgr get-updates 1e8c8470-a49c-571a-82fd-19c9fa32b8c3

And to see if it indicates it’s truly busy:

fprintd-enroll

If it asks you to place a fingerprint onto the reader for enrollment, the GUI is wrong. If it replicates the error that it’s in use or busy, then we’d want to get this into a ticket,

Sounds good, and just to clarify, I installed the firmware update using the CLI as described in the docs. It’s just that ever since then Gnome Software shows this weird error after updates that require a reboot.

Here’s the info you asked for:

% fwupdmgr get-devices 1e8c8470-a49c-571a-82fd-19c9fa32b8c3
Selected device: Fingerprint Sensor
Framework Laptop 13 (AMD Ryzen 7040Series)
│
└─Fingerprint Sensor:
      Device ID:          23ec719b6aabc2d2dac5176c232f0da7a21881b0
      Summary:            Match-On-Chip fingerprint sensor
      Current version:    01000334
      Vendor:             Goodix (USB:0x27C6)
      Install Duration:   10 seconds
      Serial Number:      UIDDE76F500_XXXX_MOC_B0
      GUID:               1e8c8470-a49c-571a-82fd-19c9fa32b8c3 ← USB\VID_27C6&PID_609C
      Device Flags:       • Updatable
                          • Device stages updates
                          • Device can recover flash failures
                          • Signed Payload

fprintd showed an authn pop-up and, after I authenticated, proceeded to have me enroll my fingerprint (I Ctrl+C’d out of it):

% fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.

So the GUI is wrong, it seems. I have everything working perfectly, I just want to stop Gnome Software from complaining. Is there a way to do that?

Thanks for helping out!

I realize that this is an old thread, but I’ve experienced this same issue since April as well. Was this ever solved or even placed into a ticket?

No, not as far as I’m aware. I ended up reinstalling my system for a different reason though so I no longer have this issue.