Repository navigation
Conversation
Re-running setup used to exit on enroll-duplicate before writing PAM, leaving enrolled prints unusable for sudo/polkit/lock. Detect existing prints via fprintd-list, offer to skip enroll, and still configure PAM when enroll fails but prints remain. Co-authored-by: AnPod <AnPod@users.noreply.github.com>
c9fa5bd to
61f7848
Compare
|
Reviewed against It is one of three open pull requests for #13433, and #13542 is the one brought forward. Both fix the bug the same way at the core (detect a saved print with
#13467 does not detect a saved print at all ( Nothing was run for this pull request: with #13542 carrying the fix, a worker run here would test a branch that is not the candidate. The comparison was read from the three diffs and the base scripts, by Claude Opus 5.5 and by Codex Medium as a second opinion, which was asked to pick between the three without being given an answer. It also chose #13542 and raised the prompt-cancel case above. It can read this session's notes, so its agreement is not a guaranteed independent check. Waiting on the maintainer to choose between #13542 and this one. |
Fixes #13433
omarchy setup security fingerprintonly wrote PAM after a successful enroll. If a print was already enrolled,fprintd-enrollfailed withenroll-duplicateand exited before PAM was configured.fprintd-listand offer to skip enroll / configure PAMDraft.