Recover when Omarchy's fingerprint setup fails because a print is already enrolled
Re-read /usr/share/omarchy/bin/omarchy-setup-security-fingerprint and omarchy-remove-security-fingerprint on 4.0.4-1. The earlier correction holds: setup_pam_config and setup_lock_fingerprint_pam run only inside the success branch of sudo fprintd-enroll "$USER" and then fprintd-verify, the else branch prints Enrollment failed. Please try again. and exits 1, and the remove script strips PAM lines, deletes /etc/pam.d/omarchy-lock-fingerprint and runs omarchy-pkg-drop fprintd libfprint libfprint-git with no fprintd-delete. Issue #13433 (open, filed on 4.0.4-1) matches the symptom, the enroll-duplicate output and the transfer failed reader wedge. Diffing against the quattro branch (upstream latest release is still v4.0.4) found that unreleased quattro now has the remove script run rm -rf /var/lib/fprint/$fingerprint_user, while the setup script still exits on any enroll failure. The fix gains one paragraph saying so, so a reader on a later release knows which half is fixed. Cause, symptom, danger and verify are unchanged. Not exercised: no fingerprint reader here.
fprintd-delete "$USER" removes every enrolled finger for that user. Re-enroll before relying on the fingerprint again.
Symptom
omarchy setup security fingerprint fails with Enrollment failed. Please try again. every time it is re-run, and the fingerprint is never used for sudo, polkit or the lock screen. fprintd-enroll prints Enroll result: enroll-duplicate. fprintd-verify matches, but grep pam_fprintd /etc/pam.d/sudo finds nothing and /etc/pam.d/omarchy-lock-fingerprint does not exist.
Cause
omarchy-setup-security-fingerprint only writes the PAM configuration (setup_pam_config and setup_lock_fingerprint_pam) inside the success branch of sudo fprintd-enroll "$USER" followed by fprintd-verify. Once a print exists, enrolling the same finger returns enroll-duplicate and exits non-zero, so the script exits 1 before reaching PAM. omarchy-remove-security-fingerprint strips PAM lines and drops the packages but never runs fprintd-delete, so the print in /var/lib/fprint/ survives and remove-then-setup lands in the same state. Confirmed by reading both scripts on 4.0.4-1.
Fix
Delete the stored prints, then run the wizard so enrollment succeeds and PAM is written:
fprintd-list "$USER"
sudo fprintd-delete "$USER"
fprintd-list "$USER" # should report no fingers enrolled
omarchy setup security fingerprint
If fprintd-list is not found, you ran omarchy-remove-security-fingerprint, which uninstalls fprintd but leaves the prints in /var/lib/fprint/. Run omarchy setup security fingerprint once so it reinstalls the packages (it will fail again at enrollment), then run the fprintd-delete sequence above and the wizard a second time.
Run the wizard as your user, not with sudo. The Omarchy scripts call sudo themselves and sudo omarchy-... loses OMARCHY_PATH.
If fprintd-enroll instead fails with Open failed with error: transfer failed, the reader has wedged from repeated attempts. Wait for it to re-enumerate (journalctl -k -f shows USB disconnect then new full-speed USB device) before retrying.
On the upstream quattro branch after 4.0.4, the remove script also deletes /var/lib/fprint/<user>, so once that ships remove-then-setup recovers by itself. The setup script there still exits on enroll-duplicate, so fprintd-delete stays the fix when a print is enrolled and PAM is not configured.
Verify
grep -n pam_fprintd /etc/pam.d/sudo
ls -l /etc/pam.d/omarchy-lock-fingerprint
sudo -k && sudo true # should ask for a fingerprint