Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-4706GitHub issuePublicReceived

omarchy-hw-fingerprint doesn't detect Broadcom (0a5c) fingerprint sensors

Reported by gbillium143 · filed Aug 26, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #7424 (R-1672). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
Not yet mapped to any requirement or component.
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

omarchy-hw-fingerprint doesn't detect Broadcom (0a5c) fingerprint sensorsrevision 1 · captured 2026-10-04 12:03 UTC via poll

What happened

omarchy setup security fingerprint fails immediately with "No fingerprint sensor detected," even though a fingerprint reader is present, enabled in BIOS, and fully supported by fprintd/libfprint-tod.

The reader is a Broadcom sensor:
- USB path: /sys/bus/usb/devices/3-8
- idVendor: 0a5c (Broadcom Corp)
- idProduct: 5843
- product string: 58200 (no "fingerprint"/"biometric" text)
- No kernel driver bound to its interface (as expected — libfprint drives it from userspace)

omarchy-hw-fingerprint's detection gate only matches a fixed vendor allowlist (27c6 138a 06cb 08ff 1c7a 147e) plus a product-string match for "fingerprint"/"biometric"/etc. Since Broadcom (0a5c) isn't in that list and the product string is a bare model number, the gate returns false and the wizard bails before even installing fprintd.

Once fprintd/libfprint-tod/usbutils are installed manually, fprintd-list correctly detects the device as "Broadcom Sensors", and enrollment/verification work fine — the reader itself is fully functional, only the detection gate is wrong.

What was expected

omarchy setup security fingerprint to detect the Broadcom sensor and proceed with setup.

Steps to reproduce

  1. On a laptop with a Broadcom USB fingerprint sensor (vendor 0a5c), enable it in BIOS.
  2. Run omarchy setup security fingerprint.
  3. Observe: "No fingerprint sensor detected." and the wizard exits.
  4. Manually install fprintd usbutils and run fprintd-list "$USER" — the device is found immediately as "Broadcom Sensors".

Suggested fix

Add 0a5c (Broadcom) to the fingerprint_vendors allowlist in omarchy-hw-fingerprint (/usr/share/omarchy/bin/omarchy-hw-fingerprint or equivalent source location).

System details

  • Omarchy version: 4.0.1-1
  • CPU: 13th Gen Intel(R) Core(TM) i7-1365U
  • GPU: Intel Iris Xe Graphics (Raptor Lake-P)
  • Kernel: 7.1.9-arch1-2
  • fprintd: 1.94.5-2
  • libfprint-tod: 1.95.2+tod1-1
View raw text
### What happened

`omarchy setup security fingerprint` fails immediately with "No fingerprint sensor detected," even though a fingerprint reader is present, enabled in BIOS, and fully supported by `fprintd`/`libfprint-tod`.

The reader is a Broadcom sensor:
- USB path: `/sys/bus/usb/devices/3-8`
- `idVendor`: `0a5c` (Broadcom Corp)
- `idProduct`: `5843`
- `product` string: `58200` (no "fingerprint"/"biometric" text)
- No kernel driver bound to its interface (as expected — libfprint drives it from userspace)

`omarchy-hw-fingerprint`'s detection gate only matches a fixed vendor allowlist (`27c6 138a 06cb 08ff 1c7a 147e`) plus a product-string match for "fingerprint"/"biometric"/etc. Since Broadcom (`0a5c`) isn't in that list and the product string is a bare model number, the gate returns false and the wizard bails before even installing `fprintd`.

Once `fprintd`/`libfprint-tod`/`usbutils` are installed manually, `fprintd-list` correctly detects the device as **"Broadcom Sensors"**, and enrollment/verification work fine — the reader itself is fully functional, only the detection gate is wrong.

### What was expected

`omarchy setup security fingerprint` to detect the Broadcom sensor and proceed with setup.

### Steps to reproduce

1. On a laptop with a Broadcom USB fingerprint sensor (vendor `0a5c`), enable it in BIOS.
2. Run `omarchy setup security fingerprint`.
3. Observe: "No fingerprint sensor detected." and the wizard exits.
4. Manually install `fprintd usbutils` and run `fprintd-list "$USER"` — the device is found immediately as "Broadcom Sensors".

### Suggested fix

Add `0a5c` (Broadcom) to the `fingerprint_vendors` allowlist in `omarchy-hw-fingerprint` (`/usr/share/omarchy/bin/omarchy-hw-fingerprint` or equivalent source location).

### System details

- Omarchy version: 4.0.1-1
- CPU: 13th Gen Intel(R) Core(TM) i7-1365U
- GPU: Intel Iris Xe Graphics (Raptor Lake-P)
- Kernel: 7.1.9-arch1-2
- `fprintd`: 1.94.5-2
- `libfprint-tod`: 1.95.2+tod1-1

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.