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-1823GitHub issuePublicDecided· Out of scope

setup security fingerprint fails on sensors requiring open-fprintd (ThinkPad 06cb:009a)

Reported by ItsNotPaths · filed Aug 15, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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

setup security fingerprint fails on sensors requiring open-fprintd (ThinkPad 06cb:009a)revision 1 · captured 2026-09-28 21:29 UTC via poll

What happened

omarchy setup security fingerprint cannot complete on hardware whose fingerprint
sensor is unsupported by libfprint and requires the open-fprintd +
python-validity stack instead. This covers a large slice of ThinkPads, including
the T480/T480s/T490/X1C6 family (Synaptics/Validity 06cb:009a).

install/../omarchy-setup-security-fingerprint hardcodes stock fprintd:

omarchy-pkg-add libfprint fprintd usbutils

On a machine already running the working stack, this aborts the whole command:

:: fprintd-1.94.5-2 and fprintd-clients-git-1.90.1.r2.g54e56d6-10 are in conflict.
   Remove fprintd-clients-git? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)

Answering y is not a viable workaround: it reinstalls the libfprint-backed
daemon, which does not support the sensor, so the reader stops being detected at all.

Why this is only a packaging problem

Everything in the script after that line works correctly on the alternate stack.
open-fprintd implements the same net.reactivated.Fprint D-Bus interface, and
fprintd-clients-git provides both the CLI tools and pam_fprintd.so at the same
path Omarchy expects:

$ pacman -Qo /usr/lib/security/pam_fprintd.so
/usr/lib/security/pam_fprintd.so is owned by fprintd-clients-git 1.90.1.r2.g54e56d6-10

$ fprintd-list $USER
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Fingerprints for user … on DBus driver (press):
 - #0: right-index-finger

Environment

  • Omarchy 4.0.0-1
  • Kernel 7.1.8-arch1-3
  • ThinkPad T480s (20L7S2QV00)
  • Sensor: 06cb:009a Synaptics Metallica MIS Touch Fingerprint Reader
  • Stack: python-validity 0.15-1, open-fprintd 0.7-2, fprintd-clients-git 1.90.1.r2.g54e56d6-10
View raw text
## What happened

`omarchy setup security fingerprint` cannot complete on hardware whose fingerprint
sensor is unsupported by `libfprint` and requires the `open-fprintd` +
`python-validity` stack instead. This covers a large slice of ThinkPads, including
the T480/T480s/T490/X1C6 family (Synaptics/Validity `06cb:009a`).

`install/../omarchy-setup-security-fingerprint` hardcodes stock `fprintd`:

```bash
omarchy-pkg-add libfprint fprintd usbutils
```

On a machine already running the working stack, this aborts the whole command:

```
:: fprintd-1.94.5-2 and fprintd-clients-git-1.90.1.r2.g54e56d6-10 are in conflict.
   Remove fprintd-clients-git? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
```

Answering `y` is not a viable workaround: it reinstalls the `libfprint`-backed
daemon, which does not support the sensor, so the reader stops being detected at all.

## Why this is only a packaging problem

Everything in the script *after* that line works correctly on the alternate stack.
`open-fprintd` implements the same `net.reactivated.Fprint` D-Bus interface, and
`fprintd-clients-git` provides both the CLI tools and `pam_fprintd.so` at the same
path Omarchy expects:

```
$ pacman -Qo /usr/lib/security/pam_fprintd.so
/usr/lib/security/pam_fprintd.so is owned by fprintd-clients-git 1.90.1.r2.g54e56d6-10

$ fprintd-list $USER
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Fingerprints for user … on DBus driver (press):
 - #0: right-index-finger
```

## Environment

- Omarchy 4.0.0-1
- Kernel 7.1.8-arch1-3
- ThinkPad T480s (20L7S2QV00)
- Sensor: `06cb:009a` Synaptics Metallica MIS Touch Fingerprint Reader
- Stack: `python-validity` 0.15-1, `open-fprintd` 0.7-2, `fprintd-clients-git` 1.90.1.r2.g54e56d6-10

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 04:12 UTC