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 feedback OSD remains stuck after Cursor and Grok Bot launch
Reported by aj-ebels · filed Sep 2, 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
System details
Omarchy: 4.0.2-1 Hyprland: 0.56.2-1 Quickshell: 0.3.1-1 Kernel: 7.1.9-arch1-2 Desktop/session: Wayland / Hyprland Hardware: Dell XPS 13 DX13260 CPU: Intel Core 5 320 GPU: Intel Wildcat Lake, xe driver Display: 2560x1600 internal display
What's wrong?
The Omarchy launch-feedback OSD remains stuck indefinitely after launching applications from the Omarchy application menu.
This has occurred with both Cursor and Grok Bot. The applications launch successfully and their windows appear normally, but the OSD remains visible showing:
Launching Grok Bot…
The same behavior previously occurred with Cursor.
The OSD should disappear when the application window appears, or after the documented 15-second failsafe timeout. Instead, it remains visible indefinitely.
I confirmed that both applications are running and registered correctly in Hyprland:
- Cursor: class
cursor - Grok Bot: class
grok-bot
The stuck OSD can be manually dismissed with: omarchy-shell osd close
The installed /usr/share/omarchy/shell/services/AppLibrary.qml shows the launch OSD with duration: 0, then attempts to close it when a new toplevel appears or after 15 seconds.
Neither automatic cleanup path appears to work in this case.
The attached debug log and screenshot provide additional details.
<img width="578" height="180" alt="Image" src="https://github.com/user-attachments/assets/be3693a7-9c9e-467a-833d-508da3b3d669" />
View raw text
### System details Omarchy: 4.0.2-1 Hyprland: 0.56.2-1 Quickshell: 0.3.1-1 Kernel: 7.1.9-arch1-2 Desktop/session: Wayland / Hyprland Hardware: Dell XPS 13 DX13260 CPU: Intel Core 5 320 GPU: Intel Wildcat Lake, xe driver Display: 2560x1600 internal display ### What's wrong? The Omarchy launch-feedback OSD remains stuck indefinitely after launching applications from the Omarchy application menu. This has occurred with both Cursor and Grok Bot. The applications launch successfully and their windows appear normally, but the OSD remains visible showing: Launching Grok Bot… The same behavior previously occurred with Cursor. The OSD should disappear when the application window appears, or after the documented 15-second failsafe timeout. Instead, it remains visible indefinitely. I confirmed that both applications are running and registered correctly in Hyprland: - Cursor: class `cursor` - Grok Bot: class `grok-bot` The stuck OSD can be manually dismissed with: omarchy-shell osd close The installed `/usr/share/omarchy/shell/services/AppLibrary.qml` shows the launch OSD with `duration: 0`, then attempts to close it when a new toplevel appears or after 15 seconds. Neither automatic cleanup path appears to work in this case. The attached debug log and screenshot provide additional details. <img width="578" height="180" alt="Image" src="https://github.com/user-attachments/assets/be3693a7-9c9e-467a-833d-508da3b3d669" /> [omarchy-debug.log](https://github.com/user-attachments/files/31741006/omarchy-debug.log)
- omarchy-debug.log
- be3693a7-9c9e-467a-833d-508da3b3d669
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 10:36 UTC