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-4715GitHub issuePublicReceived

omarchy-hw-fingerprint doesn't detect Dell ControlVault 3 (Broadcom 0a5c:5843)

Reported by VardanMelkonyan · filed Aug 27, 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 Dell ControlVault 3 (Broadcom 0a5c:5843)revision 1 · captured 2026-10-04 12:03 UTC via poll

What happened

omarchy setup security fingerprint fails with "No fingerprint sensor detected", even though a working fingerprint reader is present and fully functional at the fprintd/libfprint layer.

  • lsusb shows: Bus 003 Device 003: ID 0a5c:5843 Broadcom Corp. BCM58200 ControlVault 3 (FingerPrint sensor + Contacted SmartCard)
  • After manually installing the AUR package libfprint-2-tod1-broadcom (proprietary TOD driver explicitly built for device ID 0a5c:5843) and restarting fprintd, the sensor works correctly:
  • fprintd-list "$USER" finds the device and lists an enrolled finger
  • fprintd-verify starts a verify session and waits for a touch as expected
  • However, omarchy setup security fingerprint still prints "No fingerprint sensor detected" and exits before doing anything (package install, enrollment, PAM config).

Root cause

omarchy-hw-fingerprint gates detection on either:
1. The USB product string descriptor containing "fingerprint"/"biometric"/etc., or
2. The idVendor matching a hardcoded allow-list: 27c6 138a 06cb 08ff 1c7a 147e

This device's vendor ID is 0a5c (Broadcom), which isn't in the list, and the actual USB string descriptor for this device is just "58200" (no "fingerprint"/"biometric" substring) — lsusb's friendly name comes from its own bundled usb.ids database, not the device's own descriptor, so the product-string heuristic can't catch it either. As a result the script exits 1 and the wizard bails before checking whether a TOD driver package could actually handle it.

What I expected

Since a proprietary libfprint TOD driver exists specifically for this device ID (libfprint-2-tod1-broadcom on AUR, sourced from Dell's Ubuntu OEM repo for the Latitude 7300, which ships firmware/driver keyed to 0a5c:5843), I'd expect omarchy-hw-fingerprint to at least recognize Dell ControlVault 3 readers (vendor 0a5c) as detectable, so the wizard can proceed to install libfprint-2-tod1-broadcom and enroll normally.

Steps to reproduce

  1. On a Dell laptop with a ControlVault 3 fingerprint reader (0a5c:5843), run omarchy setup security fingerprint.
  2. Observe it prints "No fingerprint sensor detected" and exits immediately.
  3. Confirm the reader is real: install libfprint-2-tod1-broadcom from AUR, sudo systemctl restart fprintd, then fprintd-list "$USER" — it finds the device.

System details

  • Omarchy version: 4.0.1-1
  • Kernel: 7.1.9-arch1-2
  • CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
  • GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
  • Fingerprint reader: Broadcom BCM58200 ControlVault 3 (FingerPrint sensor + Contacted SmartCard), USB ID 0a5c:5843
  • Driver used to confirm it works: AUR libfprint-2-tod1-broadcom 5.15.021.0-1 (+ libfprint-tod dependency)
View raw text
## What happened

`omarchy setup security fingerprint` fails with "No fingerprint sensor detected", even though a working fingerprint reader is present and fully functional at the fprintd/libfprint layer.

- `lsusb` shows: `Bus 003 Device 003: ID 0a5c:5843 Broadcom Corp. BCM58200 ControlVault 3 (FingerPrint sensor + Contacted SmartCard)`
- After manually installing the AUR package `libfprint-2-tod1-broadcom` (proprietary TOD driver explicitly built for device ID `0a5c:5843`) and restarting `fprintd`, the sensor works correctly:
  - `fprintd-list "$USER"` finds the device and lists an enrolled finger
  - `fprintd-verify` starts a verify session and waits for a touch as expected
- However, `omarchy setup security fingerprint` still prints "No fingerprint sensor detected" and exits before doing anything (package install, enrollment, PAM config).

## Root cause

`omarchy-hw-fingerprint` gates detection on either:
1. The USB `product` string descriptor containing "fingerprint"/"biometric"/etc., or
2. The `idVendor` matching a hardcoded allow-list: `27c6 138a 06cb 08ff 1c7a 147e`

This device's vendor ID is `0a5c` (Broadcom), which isn't in the list, and the actual USB string descriptor for this device is just `"58200"` (no "fingerprint"/"biometric" substring) — `lsusb`'s friendly name comes from its own bundled `usb.ids` database, not the device's own descriptor, so the product-string heuristic can't catch it either. As a result the script exits 1 and the wizard bails before checking whether a TOD driver package could actually handle it.

## What I expected

Since a proprietary libfprint TOD driver exists specifically for this device ID (`libfprint-2-tod1-broadcom` on AUR, sourced from Dell's Ubuntu OEM repo for the Latitude 7300, which ships firmware/driver keyed to `0a5c:5843`), I'd expect `omarchy-hw-fingerprint` to at least recognize Dell ControlVault 3 readers (vendor `0a5c`) as detectable, so the wizard can proceed to install `libfprint-2-tod1-broadcom` and enroll normally.

## Steps to reproduce

1. On a Dell laptop with a ControlVault 3 fingerprint reader (`0a5c:5843`), run `omarchy setup security fingerprint`.
2. Observe it prints "No fingerprint sensor detected" and exits immediately.
3. Confirm the reader is real: install `libfprint-2-tod1-broadcom` from AUR, `sudo systemctl restart fprintd`, then `fprintd-list "$USER"` — it finds the device.

## System details

- Omarchy version: 4.0.1-1
- Kernel: 7.1.9-arch1-2
- CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
- GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
- Fingerprint reader: Broadcom BCM58200 ControlVault 3 (FingerPrint sensor + Contacted SmartCard), USB ID `0a5c:5843`
- Driver used to confirm it works: AUR `libfprint-2-tod1-broadcom` 5.15.021.0-1 (+ `libfprint-tod` dependency)

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.