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.
Launch OSD toast ("Launching X…") can get stuck on screen indefinitely
Reported by PandaProgrammierer · filed Sep 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
What happened
Launched Brave via the app launcher while a Brave window was already open/running. The "Launching Brave…" OSD toast (rocket icon) appeared and then never disappeared again — it stayed on screen for several minutes until manually cleared.
What I expected
The launch-feedback OSD should auto-close once the app's window is focused, or at the latest after the 15s fallback timeout.
Steps to reproduce
- Have an app (e.g. Brave) already running with an open window.
- Launch it again from the Omarchy app launcher (or
gtk-launch brave-browser.desktop). - Since no new toplevel is created, the launch-feedback OSD ("Launching Brave…") is shown after the ~2s delay.
- In this session it never closed on its own — it was still showing several minutes later, well past the 15s
launchTimeoutfallback inAppLibrary.qmlthat should callcloseLaunchFeedback()->Quickshell.execDetached(["omarchy-shell", "osd", "close"]).
Workaround found
Running omarchy-shell osd close manually closed the stuck toast immediately.
Note: omarchy notification dismiss "Brave" did not clear it — this OSD toast is driven by AppLibrary.qml's launch-feedback state machine, not the notification service, so that command is a no-op here.
Relevant source
/usr/share/omarchy/shell/services/AppLibrary.qml, beginLaunchFeedback / closeLaunchFeedback / maybeFinishLaunchFeedback (~lines 160-253). The 15000ms launchTimeout Timer should force-close the OSD via closeLaunchFeedback, but in this case the toast persisted well beyond that.
System
- Omarchy 4.0.4-1
- Hyprland 0.56.2
- quickshell 0.3.1-1
- HP EliteBook 845 G8 (AMD Ryzen 5 PRO 5650U, integrated Radeon)
Screenshot
Stuck "Launching Brave…" toast (green border, rocket icon):
<!-- attach screenshot after creation if desired -->
View raw text
### What happened
Launched Brave via the app launcher while a Brave window was already open/running. The "Launching Brave…" OSD toast (rocket icon) appeared and then never disappeared again — it stayed on screen for several minutes until manually cleared.
### What I expected
The launch-feedback OSD should auto-close once the app's window is focused, or at the latest after the 15s fallback timeout.
### Steps to reproduce
1. Have an app (e.g. Brave) already running with an open window.
2. Launch it again from the Omarchy app launcher (or `gtk-launch brave-browser.desktop`).
3. Since no *new* toplevel is created, the launch-feedback OSD ("Launching Brave…") is shown after the ~2s delay.
4. In this session it never closed on its own — it was still showing several minutes later, well past the 15s `launchTimeout` fallback in `AppLibrary.qml` that should call `closeLaunchFeedback()` -> `Quickshell.execDetached(["omarchy-shell", "osd", "close"])`.
### Workaround found
Running `omarchy-shell osd close` manually closed the stuck toast immediately.
Note: `omarchy notification dismiss "Brave"` did *not* clear it — this OSD toast is driven by `AppLibrary.qml`'s launch-feedback state machine, not the notification service, so that command is a no-op here.
### Relevant source
`/usr/share/omarchy/shell/services/AppLibrary.qml`, `beginLaunchFeedback` / `closeLaunchFeedback` / `maybeFinishLaunchFeedback` (~lines 160-253). The 15000ms `launchTimeout` Timer should force-close the OSD via `closeLaunchFeedback`, but in this case the toast persisted well beyond that.
### System
- Omarchy 4.0.4-1
- Hyprland 0.56.2
- quickshell 0.3.1-1
- HP EliteBook 845 G8 (AMD Ryzen 5 PRO 5650U, integrated Radeon)
### Screenshot
Stuck "Launching Brave…" toast (green border, rocket icon):
<!-- attach screenshot after creation if desired -->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 20:04 UTC