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 ("Launching <app>…") can stay on screen forever
Reported by walteraandrade · 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
System details
Intel i7-12700H, Intel Iris Xe + NVIDIA RTX 3060 Mobile, Omarchy 4.0.4-1, quickshell 0.3.1-1, Hyprland 0.56.2-2
What's wrong?
After launching Claude Desktop from the app launcher, the launch OSD ("Launching Claude…") stayed on screen indefinitely, long after the app window was open and in use. It survived restarting the app (including under --ozone-platform=x11). hyprctl layers showed it on the omarchy-osd layer owned by quickshell -n -p /usr/share/omarchy/shell. Running omarchy-shell osd close removed it.
In shell/services/AppLibrary.qml, launchDelay shows the OSD with duration: 0, so it only goes away if a later omarchy-shell osd close lands. That close is issued by closeLaunchFeedback (new toplevel/active-window change, or launchTimeout after 15 s). Both show and close go through Quickshell.execDetached, so nothing orders them; if the close is lost or runs before the show (or state is reset while the OSD is open), nothing ever dismisses it. I haven't pinned down the exact trigger, it's not reproducible on demand.
Suggested fix: give the launch OSD a finite duration (e.g. the same 15000 ms as launchTimeout) so a missed close can't leave it up forever.
View raw text
### System details
Intel i7-12700H, Intel Iris Xe + NVIDIA RTX 3060 Mobile, Omarchy 4.0.4-1, quickshell 0.3.1-1, Hyprland 0.56.2-2
### What's wrong?
After launching Claude Desktop from the app launcher, the launch OSD ("Launching Claude…") stayed on screen indefinitely, long after the app window was open and in use. It survived restarting the app (including under `--ozone-platform=x11`). `hyprctl layers` showed it on the `omarchy-osd` layer owned by `quickshell -n -p /usr/share/omarchy/shell`. Running `omarchy-shell osd close` removed it.
In `shell/services/AppLibrary.qml`, `launchDelay` shows the OSD with `duration: 0`, so it only goes away if a later `omarchy-shell osd close` lands. That close is issued by `closeLaunchFeedback` (new toplevel/active-window change, or `launchTimeout` after 15 s). Both `show` and `close` go through `Quickshell.execDetached`, so nothing orders them; if the close is lost or runs before the show (or state is reset while the OSD is open), nothing ever dismisses it. I haven't pinned down the exact trigger, it's not reproducible on demand.
Suggested fix: give the launch OSD a finite `duration` (e.g. the same 15000 ms as `launchTimeout`) so a missed close can't leave it up forever.
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 20:02 UTC