Skip to content

Name Touch ID as a fingerprint reader - #43

Closed
RyanTheTide wants to merge 1 commit into
omacom:mainfrom
aurora-silicon:touchid/fingerprint-reader-list
Closed

RyanTheTide wants to merge 1 commit into
omacom:mainfrom
aurora-silicon:touchid/fingerprint-reader-list

Conversation

@RyanTheTide

Copy link
Copy Markdown

Problem

omarchy-hw-fingerprint (omacom/omarchy#14675) can only recognise a reader that the kernel drives without USB through /usr/share/omarchy-platform/fingerprint-readers. No package ships that file, so on a Mac with Touch ID, Omarchy's fingerprint setup says "No fingerprint sensor detected".

Change

omarchy-mac ships the file with one entry:

/sys/bus/platform/drivers/apple_sep/*/diag/touchid ready

In linux-aurora (drivers/soc/apple/diag_shim.c at omacom/linux-aurora 44d5afc79da7), diag/touchid reads ready only after Touch ID has started and the sensor is online. It reads not-ready, failed or unknown otherwise. A Mac that has not brought Touch ID up therefore still gets no invitation, and a USB reader is still found.

Overlap with #12 (@scottjones): this is the reader-list part of #12 on its own. The line, the desktop-setup assertion, fingerprint-readers-test.sh, the runtime pin (81fd2d23, the merge of omacom/omarchy#14675) and the omarchy-i18n fix to the factory-reset test are byte-identical to #12, so either PR rebases cleanly over the other. This PR leaves out #12's activation unit, udev rule, alpm hook, fprintd drop-in, sleep hook and version bump. #12's README says to ship this file only once a stock boot enrols. That gate holds here because the file only matches once the owner has brought Touch ID to ready. Whether that is enough, given that calibration can be missing even while the sensor reads ready, is your call, Scott.

Tests

The CI workflow's Arch container steps, run on the buildbox against runtime 81fd2d23:

  • test/integration/fingerprint-readers-test.sh passes (2/2): Touch ID is found only once it reads ready, and a not-ready Touch ID leaves a USB reader to be found.
  • omarchy-mac/test/desktop-setup-test.sh passes, so fingerprint-readers is staged in the platform root with the exact line.
  • On every other suite file the branch is no worse than main against the same runtime. mpv, factory-reset-luks, mac-update-boot-verify, snapshot-restore-mac and provision-owner-luks (which hangs) fail identically on unmodified main in that container.

🤖 Generated with Claude Code

omarchy-hw-fingerprint recognises a reader the kernel drives without
USB only through /usr/share/omarchy-platform/fingerprint-readers, and
no package shipped one, so Omarchy's fingerprint setup said "No
fingerprint sensor detected" on a Mac with Touch ID.

Ship the file with the Secure Enclave driver's diag/touchid, which reads
"ready" once the sensor is bound and its fingerprints are restored. The
line is the one in Scott Jones's omacom#12, which carries the rest of the
Touch ID integration.

Test against the runtime merge of omacom/omarchy#14675, which reads the
file, and give the factory-reset test that runtime's omarchy-i18n (both
from omacom#12).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@RyanTheTide

Copy link
Copy Markdown
Author

Closing this in favour of #12. It's a byte-identical subset of #12, and on its own it would do harm: Omarchy would show the one-time fingerprint invitation as soon as diag/touchid reads ready, but stock fprintd still can't open /dev/sep-bio until the sandbox drop-in ships, so setup couldn't finish. The gating belongs with #12. I've left a note there.

@RyanTheTide
RyanTheTide deleted the touchid/fingerprint-reader-list branch October 20, 2026 01:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant