Automated post-install setup of Ubuntu 20.04 and 22.04 on the Framework

Every time I try to run that it says command not found.

It’s not a command. The command to check fprintd.service's status is

sudo systemctl status fprintd.service

Running this script gives me the following:

<__gi__.FpiDeviceGoodixMoc object at 0x7f4e2bafa900 (FpiDeviceGoodixMoc at 0x55d8eb2cd1e0)>
goodixmoc
UID342C7CF8_XXXX_MOC_B0

(process:41848): libfprint-ERROR **: 21:22:20.129: parse fingerlist error
Trace/breakpoint trap

But I am also having the same issue as @Sam_Lane when trying to register fingerprints.

And here is the status of the frpints.service:

○ fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/lib/systemd/system/fprintd.service; static)
     Active: inactive (dead)
       Docs: man:fprintd(1)

May 23 15:46:35 frame010 systemd[1]: fprintd.service: Deactivated successfully.
May 23 16:16:38 frame010 systemd[1]: Starting Fingerprint Authentication Daemon...
May 23 16:16:38 frame010 systemd[1]: Started Fingerprint Authentication Daemon.
May 23 16:17:09 frame010 systemd[1]: fprintd.service: Deactivated successfully.
May 23 17:04:17 frame010 systemd[1]: Starting Fingerprint Authentication Daemon...
May 23 17:04:18 frame010 systemd[1]: Started Fingerprint Authentication Daemon.
May 23 21:03:49 frame010 systemd[1]: fprintd.service: Deactivated successfully.
May 23 21:22:16 frame010 systemd[1]: Starting Fingerprint Authentication Daemon...
May 23 21:22:17 frame010 systemd[1]: Started Fingerprint Authentication Daemon.
May 23 21:22:47 frame010 systemd[1]: fprintd.service: Deactivated successfully.

The fingerprint reader is the only thing not working currently. It isn’t a big deal, but I am curious about why it is having issues. I have been able to use it before when I had 18.04 on here.

The service log looks fine in your case. Something else is up. Not sure what. I don’t know how to interpret the sudo libfprint_delete_device_prints.py -d log. Maybe it has to do with “another OS claiming ownership of the reader”? I don’t actually understand that mechanism well.

Maybe this is related? Although you’ve been there before. Maybe in the past.

Ahhh. That makes sense. Sorry about that. Here are the results:

× fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/lib/systemd/system/fprintd.service; static)
Active: failed (Result: exit-code) since Tue 2022-05-24 21:13:37 CEST; 30s>
Docs: man:fprintd(1)
Process: 6495 ExecStart=/usr/libexec/fprintd (code=exited, status=127)
Main PID: 6495 (code=exited, status=127)
CPU: 72ms

May 24 21:13:37 samlane86-Laptop systemd[1]: Starting Fingerprint Authenticatio>
May 24 21:13:37 samlane86-Laptop fprintd[6495]: /usr/libexec/fprintd: symbol lo>
May 24 21:13:37 samlane86-Laptop systemd[1]: fprintd.service: Main process exit>
May 24 21:13:37 samlane86-Laptop systemd[1]: fprintd.service: Failed with resul>
May 24 21:13:37 samlane86-Laptop systemd[1]: Failed to start Fingerprint Authen>
lines 1-13/13 (END)…skipping…
× fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/lib/systemd/system/fprintd.service; static)
Active: failed (Result: exit-code) since Tue 2022-05-24 21:13:37 CEST; 30s ago
Docs: man:fprintd(1)
Process: 6495 ExecStart=/usr/libexec/fprintd (code=exited, status=127)
Main PID: 6495 (code=exited, status=127)
CPU: 72ms

May 24 21:13:37 samlane86-Laptop systemd[1]: Starting Fingerprint Authentication Daemon…
May 24 21:13:37 samlane86-Laptop fprintd[6495]: /usr/libexec/fprintd: symbol lookup error: /usr/libexec/fprintd: undefined symbo>
May 24 21:13:37 samlane86-Laptop systemd[1]: fprintd.service: Main process exited, code=exited, status=127/n/a
May 24 21:13:37 samlane86-Laptop systemd[1]: fprintd.service: Failed with result ‘exit-code’.
May 24 21:13:37 samlane86-Laptop systemd[1]: Failed to start Fingerprint Authentication Daemon.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-13/13 (END)

× fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/lib/systemd/system/fprintd.service; static)
Active: failed (Result: exit-code) since Tue 2022-05-24 21:13:37 CEST; 30s ago
Docs: man:fprintd(1)
Process: 6495 ExecStart=/usr/libexec/fprintd (code=exited, status=127)
Main PID: 6495 (code=exited, status=127)
CPU: 72ms

May 24 21:13:37 samlane86-Laptop systemd[1]: Starting Fingerprint Authentication Daemon…
May 24 21:13:37 samlane86-Laptop fprintd[6495]: /usr/libexec/fprintd: symbol lookup error: /usr/libexec/fprintd: undefined>
May 24 21:13:37 samlane86-Laptop systemd[1]: fprintd.service: Main process exited, code=exited, status=127/n/a
May 24 21:13:37 samlane86-Laptop systemd[1]: fprintd.service: Failed with result ‘exit-code’.
May 24 21:13:37 samlane86-Laptop systemd[1]: Failed to start Fingerprint Authentication Daemon.
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-13/13 (END)

@Sam_Lane it looks like your problem is the same as @NullVoxPopuli . Check our discussion here.

Thanks! I’ll try it out!