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

Fingerprint-unlock crash (pam_fprintd) leaves orphaned duplicate Quickshell bar, unmanageable by omarchy restart shell

Reported by matiazo · filed Sep 27, 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

Fingerprint-unlock crash (pam_fprintd) leaves orphaned duplicate Quickshell bar, unmanageable by omarchy restart shellrevision 1 · captured 2026-09-28 21:23 UTC via poll

Summary

Omarchy's default fingerprint-unlock (pam_fprintd) + Quickshell-based lock screen combination can trigger a pam_fprintd segfault, which crashes the Omarchy shell (Quickshell). Quickshell's own crash-relaunch then leaves an orphaned duplicate bar on screen permanently (until manual kill or reboot), because the relaunched process is invisible to omarchy restart shell.

This is filed here for visibility/tracking since the combination is Omarchy's default config, even though the two underlying defects live upstream:

Symptom

After unlocking (often noticed after a monitor hotplug that triggers a lock/relock cycle), two Omarchy bars are visible at the top of the screen simultaneously. hyprctl layers shows two omarchy-bar / omarchy-background layers from two different quickshell PIDs; one of them has a bare /usr/bin/quickshell cmdline (no -p flag), confirming it's the orphaned crash-relaunch instance described above.

Steps to reproduce

  1. Have fingerprint unlock enabled (omarchy setup security fingerprint).
  2. Lock the session (e.g. via a monitor hotplug or omarchy system lock) and let fingerprint auth retry/timeout a few times, or trigger concurrent fingerprint auth attempts.
  3. If pam_fprintd segfaults (see linked fprintd issue), Quickshell crashes and relaunches; the relaunched instance is missing its -p flag and becomes an unmanageable duplicate bar.

Expected

A crash during lock-screen fingerprint auth should not leave a permanent duplicate bar; omarchy restart shell should be able to clean it up.

Environment

  • Omarchy: 4.0.1-1
  • Quickshell: 0.3.1-1
  • fprintd: 1.94.5-2 / libfprint: 1.94.100-1
  • Kernel: 7.1.9-arch1-2
  • CPU: Intel Core i7-8665U / GPU: Intel UHD Graphics 620

Workaround in use

A local systemd user watchdog polling hyprctl layers -j for omarchy-* layers whose owning PID's cmdline lacks -p, killing only those orphans every 5s.

View raw text
### Summary
Omarchy's default fingerprint-unlock (`pam_fprintd`) + Quickshell-based lock screen combination can trigger a `pam_fprintd` segfault, which crashes the Omarchy shell (Quickshell). Quickshell's own crash-relaunch then leaves an **orphaned duplicate bar** on screen permanently (until manual kill or reboot), because the relaunched process is invisible to `omarchy restart shell`.

This is filed here for visibility/tracking since the combination is Omarchy's default config, even though the two underlying defects live upstream:

- Quickshell (crash-relaunch drops `-p <configPath>`, so the recovered instance escapes `quickshell kill -p ...` / `omarchy restart shell`): https://github.com/quickshell-mirror/quickshell/issues/1208
- fprintd/pam_fprintd (`pam_sm_authenticate` segfaults on a `Device was already claimed` D-Bus conflict during concurrent auth attempts): to be filed at https://gitlab.freedesktop.org/libfprint/fprintd/-/issues

### Symptom
After unlocking (often noticed after a monitor hotplug that triggers a lock/relock cycle), two Omarchy bars are visible at the top of the screen simultaneously. `hyprctl layers` shows two `omarchy-bar` / `omarchy-background` layers from two different `quickshell` PIDs; one of them has a bare `/usr/bin/quickshell` cmdline (no `-p` flag), confirming it's the orphaned crash-relaunch instance described above.

### Steps to reproduce
1. Have fingerprint unlock enabled (`omarchy setup security fingerprint`).
2. Lock the session (e.g. via a monitor hotplug or `omarchy system lock`) and let fingerprint auth retry/timeout a few times, or trigger concurrent fingerprint auth attempts.
3. If `pam_fprintd` segfaults (see linked fprintd issue), Quickshell crashes and relaunches; the relaunched instance is missing its `-p` flag and becomes an unmanageable duplicate bar.

### Expected
A crash during lock-screen fingerprint auth should not leave a permanent duplicate bar; `omarchy restart shell` should be able to clean it up.

### Environment
- Omarchy: 4.0.1-1
- Quickshell: 0.3.1-1
- fprintd: 1.94.5-2 / libfprint: 1.94.100-1
- Kernel: 7.1.9-arch1-2
- CPU: Intel Core i7-8665U / GPU: Intel UHD Graphics 620

### Workaround in use
A local systemd user watchdog polling `hyprctl layers -j` for omarchy-* layers whose owning PID's cmdline lacks `-p`, killing only those orphans every 5s.

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 13:30 UTC