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.
omarchy setup security fingerprint fails instantly on Goodix 27c6:530c/533c/538c readers — no open libfprint driver exists
Reported by anupanup2001 · filed Aug 24, 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
Dell Inspiron 5585, AMD Ryzen 7 3700U, Goodix 27c6:530c fingerprint reader, Omarchy dev (4.0.0.r1816.g43bfe9b).
What's wrong?
omarchy setup security fingerprint on a Goodix 53xc-family reader (27c6:530c / 533c / 538c, found in Dell machines) detects the sensor, installs fprintd + stock libfprint, then fails within a second:
$ fprintd-list "$USER"
No devices available # exit 1
$ sudo fprintd-enroll "$USER"
Impossible to enroll: No devices available # exit 1The wizard prints "Enrollment failed. Please try again." and exits 1. Retrying can never succeed: stock libfprint has no driver for these ids at all — the goodixmoc id table starts at 27c6:5840, and 530c/533c/538c are absent from every release and from master. omarchy-hw-fingerprint correctly detects the reader beforehand (vendor 27c6, no kernel driver bound), which is exactly what makes the instant enrollment failure look transient instead of structural.
Steps to reproduce:
- Use a Dell laptop with a Goodix
27c6:530c(or533c/538c) reader - Run Setup > Security > Fingerprint (or
omarchy setup security fingerprint) - Enrollment fails immediately with no actionable message
What works
Dell ships a proprietary Linux TOD driver for this family, repackaged in the AUR as libfprint-goodix-53xc (closed binary from Dell's Ubuntu archive, dell.archive.canonical.com) on top of libfprint-tod (open libfprint fork with a vendor-plugin interface). With both installed and fprintd restarted, the device is claimed and enrollment works through the wizard's normal flow:
fprintd[...]: Creating TOD wrapper for goodix-tod (Goodix Fingerprint Sensor 53xc) driver
$ sudo fprintd-enroll
Using device /net/reactivated/Fprint/Device/1
Enroll result: enroll-stage-passed ...I verified the blob's compiled id table is exactly {27c6:530c, 27c6:533c, 27c6:538c} (its udev rule also lists 5840, which the open goodixmoc driver already covers). No PAM changes are needed — pam_fprintd.so talks to fprintd over D-Bus regardless of which driver loads underneath.
Two usage quirks worth knowing for this sensor: it is a press sensor (finger flat, hold ~1s per stage), and its firmware temporarily disables itself (Device disabled to prevent overheating) after repeated touches, recovering after a cool-down or reboot — rapid retry loops make the lockout longer (same behavior behind #7179).
Related: #1590 asked about 27c6:533c and was closed hoping for an upstream libfprint driver — these ids are still absent from libfprint master today. #7483 / #7667 cover the same shape of problem for an ELAN reader.
View raw text
Dell Inspiron 5585, AMD Ryzen 7 3700U, Goodix 27c6:530c fingerprint reader, Omarchy dev (4.0.0.r1816.g43bfe9b).
## What's wrong?
`omarchy setup security fingerprint` on a Goodix 53xc-family reader (`27c6:530c` / `533c` / `538c`, found in Dell machines) detects the sensor, installs `fprintd` + stock `libfprint`, then fails within a second:
```
$ fprintd-list "$USER"
No devices available # exit 1
$ sudo fprintd-enroll "$USER"
Impossible to enroll: No devices available # exit 1
```
The wizard prints "Enrollment failed. Please try again." and exits 1. Retrying can never succeed: stock libfprint has no driver for these ids at all — the `goodixmoc` id table starts at `27c6:5840`, and `530c`/`533c`/`538c` are absent from every release and from master. `omarchy-hw-fingerprint` correctly detects the reader beforehand (vendor 27c6, no kernel driver bound), which is exactly what makes the instant enrollment failure look transient instead of structural.
Steps to reproduce:
1. Use a Dell laptop with a Goodix `27c6:530c` (or `533c`/`538c`) reader
2. Run Setup > Security > Fingerprint (or `omarchy setup security fingerprint`)
3. Enrollment fails immediately with no actionable message
## What works
Dell ships a proprietary Linux TOD driver for this family, repackaged in the AUR as `libfprint-goodix-53xc` (closed binary from Dell's Ubuntu archive, `dell.archive.canonical.com`) on top of `libfprint-tod` (open libfprint fork with a vendor-plugin interface). With both installed and fprintd restarted, the device is claimed and enrollment works through the wizard's normal flow:
```
fprintd[...]: Creating TOD wrapper for goodix-tod (Goodix Fingerprint Sensor 53xc) driver
$ sudo fprintd-enroll
Using device /net/reactivated/Fprint/Device/1
Enroll result: enroll-stage-passed ...
```
I verified the blob's compiled id table is exactly `{27c6:530c, 27c6:533c, 27c6:538c}` (its udev rule also lists `5840`, which the open `goodixmoc` driver already covers). No PAM changes are needed — `pam_fprintd.so` talks to fprintd over D-Bus regardless of which driver loads underneath.
Two usage quirks worth knowing for this sensor: it is a **press** sensor (finger flat, hold ~1s per stage), and its firmware temporarily disables itself (`Device disabled to prevent overheating`) after repeated touches, recovering after a cool-down or reboot — rapid retry loops make the lockout longer (same behavior behind #7179).
Related: #1590 asked about `27c6:533c` and was closed hoping for an upstream libfprint driver — these ids are still absent from libfprint master today. #7483 / #7667 cover the same shape of problem for an ELAN reader.
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 08:35 UTC