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

Launcher feedback OSD can remain permanently visible

Reported by resn3t · filed Sep 19, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 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

Launcher feedback OSD can remain permanently visiblerevision 1 · captured 2026-09-28 21:23 UTC via poll
  • Bug: launcher feedback OSD can remain permanently visible after launching an app.
  • Observed: selecting a browser/web-app launcher entry shows Launching <app>… at the bottom; it never disappears when the app opens in an existing browser process/window.
  • Reproduction:
  1. Add or select any web-app desktop entry launched through omarchy-launch-webapp.
  2. Launch it from the Omarchy app launcher while the browser is already running.
  3. The launch feedback OSD remains visible indefinitely.
  • Expected: launch feedback closes after a bounded timeout, or when the launch command completes.
  • Root cause: shell/services/AppLibrary.qml starts the OSD with duration: 0 and only closes it after a Hyprland toplevel/active-toplevel change. Browser web-app launches can reuse the existing browser process and produce no observable toplevel change.
  • Suggested fix: add a finite fallback timeout to the launch OSD, and/or close feedback based on launch-process completion instead of requiring a toplevel change.
  • Version: Omarchy 4.0.4-1.
View raw text
- **Bug:** launcher feedback OSD can remain permanently visible after launching an app.
- **Observed:** selecting a browser/web-app launcher entry shows `Launching <app>…` at the bottom; it never disappears when the app opens in an existing browser process/window.
- **Reproduction:**
  1. Add or select any web-app desktop entry launched through `omarchy-launch-webapp`.
  2. Launch it from the Omarchy app launcher while the browser is already running.
  3. The launch feedback OSD remains visible indefinitely.
- **Expected:** launch feedback closes after a bounded timeout, or when the launch command completes.
- **Root cause:** `shell/services/AppLibrary.qml` starts the OSD with `duration: 0` and only closes it after a Hyprland toplevel/active-toplevel change. Browser web-app launches can reuse the existing browser process and produce no observable toplevel change.
- **Suggested fix:** add a finite fallback timeout to the launch OSD, and/or close feedback based on launch-process completion instead of requiring a toplevel change.
- **Version:** Omarchy 4.0.4-1.

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

  • Related PRpr/8570· confirmed

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 16:20 UTC