Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Fingerprint setup fails silently on FocalTech FT9366 reader (2808:a658) — migration 1785090473 assumption doesn't hold for this device ID
Reported by niels-lammers · filed Aug 28, 2026 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Title: Fingerprint setup fails silently on FocalTech FT9366 reader (2808:a658) — migration 1785090473 assumption doesn't hold for this device ID
What happened
omarchy setup security fingerprint detects the reader (via omarchy-hw-fingerprint) but enrollment never succeeds — fprintd-list reports "No devices available" and a debug run of fprintd shows:
libfprint-context-DEBUG: No driver found for USB device 2808:A658The reader is a Realtek USB2.0 Finger Print Bridge / FocalTech FT9366 sensor (USB ID 2808:a658), found on this ASUS Vivobook M6500QC.
Migration 1785090473.sh ("Switch fingerprint support back to stock libfprint") assumes FocalTech MOC support landing in libfprint 1.94.100 covers this class of hardware, and actively uninstalls libfprint-git in favor of stock libfprint. That's true for FocalTech FT9349 (2808:a97a), which the migration cites explicitly, but not for FT9366 (2808:a658) — neither stock libfprint 1.94.100 nor the current libfprint-git snapshot (1:1.94.10.r12.gd79f157-1.1) has a driver entry for this ID. I confirmed both by installing libfprint-git and re-running the same debug probe, which still reported No driver found for USB device 2808:A658.
As far as I can tell there is currently no open-source libfprint driver for this exact chip at all (only a niche, unofficial proprietary-binary shim project exists: https://github.com/leopalladium/focaltech-ft9366-arch-shim).
Expected
Either:
- omarchy-hw-fingerprint / omarchy setup security fingerprint should detect that no libfprint driver actually claims the device and fail with a clear "this reader isn't supported yet" message instead of walking through enrollment and failing opaquely, or
- if there's a known workaround Omarchy wants to support, point users at it.
Steps to reproduce
- On a machine with a FocalTech FT9366 reader (USB ID
2808:a658) behind the Realtek USB2.0 Finger Print Bridge - Run
omarchy setup security fingerprint - Detection passes, but
fprintd-enroll/fprintd-listnever see a device
System details
- Omarchy version: 4.0.1-1
- Kernel: 7.1.9-arch1-2
- CPU: AMD Ryzen 7 5800H with Radeon Graphics
- GPU: NVIDIA GeForce RTX 3050 Mobile (GA107M) + AMD Radeon Vega (Cezanne)
- Machine: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop M6500QC_M6500QC
- Fingerprint reader:
2808:a658Realtek USB2.0 Finger Print Bridge FocalTech Fingerprint Device libfprint1.94.100-1 (stock, extra repo)fprintd1.94.5-2
Diagnostic output
$ fprintd-list $USER
No devices available
$ lsusb | grep -i finger
Bus 003 Device 002: ID 2808:a658 Realtek USB2.0 Finger Print Bridge FocalTech Fingerprint Device
$ FPRINT_DEBUG=1 /usr/lib/fprintd -t
...
libfprint-context-DEBUG: No driver found for USB device 2808:A658
...
$ grep 2808 /usr/lib/udev/rules.d/70-libfprint-2.rules
(no output — vendor ID 2808 is not present in libfprint's udev rules at all)View raw text
Title: Fingerprint setup fails silently on FocalTech FT9366 reader (2808:a658) — migration 1785090473 assumption doesn't hold for this device ID
## What happened
`omarchy setup security fingerprint` detects the reader (via `omarchy-hw-fingerprint`) but enrollment never succeeds — `fprintd-list` reports "No devices available" and a debug run of `fprintd` shows:
```
libfprint-context-DEBUG: No driver found for USB device 2808:A658
```
The reader is a Realtek USB2.0 Finger Print Bridge / FocalTech FT9366 sensor (USB ID `2808:a658`), found on this ASUS Vivobook M6500QC.
Migration `1785090473.sh` ("Switch fingerprint support back to stock libfprint") assumes FocalTech MOC support landing in `libfprint` 1.94.100 covers this class of hardware, and actively uninstalls `libfprint-git` in favor of stock `libfprint`. That's true for FocalTech FT9349 (`2808:a97a`), which the migration cites explicitly, but **not** for FT9366 (`2808:a658`) — neither stock `libfprint` 1.94.100 nor the current `libfprint-git` snapshot (`1:1.94.10.r12.gd79f157-1.1`) has a driver entry for this ID. I confirmed both by installing `libfprint-git` and re-running the same debug probe, which still reported `No driver found for USB device 2808:A658`.
As far as I can tell there is currently no open-source libfprint driver for this exact chip at all (only a niche, unofficial proprietary-binary shim project exists: https://github.com/leopalladium/focaltech-ft9366-arch-shim).
## Expected
Either:
- `omarchy-hw-fingerprint` / `omarchy setup security fingerprint` should detect that no libfprint driver actually claims the device and fail with a clear "this reader isn't supported yet" message instead of walking through enrollment and failing opaquely, or
- if there's a known workaround Omarchy wants to support, point users at it.
## Steps to reproduce
1. On a machine with a FocalTech FT9366 reader (USB ID `2808:a658`) behind the Realtek USB2.0 Finger Print Bridge
2. Run `omarchy setup security fingerprint`
3. Detection passes, but `fprintd-enroll` / `fprintd-list` never see a device
## System details
- Omarchy version: 4.0.1-1
- Kernel: 7.1.9-arch1-2
- CPU: AMD Ryzen 7 5800H with Radeon Graphics
- GPU: NVIDIA GeForce RTX 3050 Mobile (GA107M) + AMD Radeon Vega (Cezanne)
- Machine: ASUSTeK COMPUTER INC. Vivobook_ASUSLaptop M6500QC_M6500QC
- Fingerprint reader: `2808:a658` Realtek USB2.0 Finger Print Bridge FocalTech Fingerprint Device
- `libfprint` 1.94.100-1 (stock, extra repo)
- `fprintd` 1.94.5-2
## Diagnostic output
```
$ fprintd-list $USER
No devices available
$ lsusb | grep -i finger
Bus 003 Device 002: ID 2808:a658 Realtek USB2.0 Finger Print Bridge FocalTech Fingerprint Device
$ FPRINT_DEBUG=1 /usr/lib/fprintd -t
...
libfprint-context-DEBUG: No driver found for USB device 2808:A658
...
$ grep 2808 /usr/lib/udev/rules.d/70-libfprint-2.rules
(no output — vendor ID 2808 is not present in libfprint's udev rules at all)
```
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.
- Out of scopeDecided by agents · verified · 2026-10-09 09:47 UTC