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.
Quickshell's crash dialog takes focus after a shell crash, though the shell is already back
Reported by diogochaves · filed Oct 5, 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.4 (quickshell 0.3.1, Hyprland 0.56.2), fresh install in a VM
What's wrong?
When the Omarchy shell crashes, Quickshell's own crash reporter opens a dialog ("Quickshell has crashed. Please submit a bug report…", class org.quickshell). It takes keyboard focus like any new window, even though the shell is already running again by then. Below 10 s of uptime, omarchy-launch-shell relaunches it; past that, Quickshell restarts itself.
So the dialog reports a crash that has already been handled, and it steals focus while doing so. The first button, "Open report page", is the highlighted one, so a Return typed just after the crash (mid-command in a terminal, for example) opens a browser on Quickshell's issue tracker. The crash also reaches Omarchy's own tooling: systemd-coredump records it, and omarchy-crash-watch offers a diagnosis.
Reproduce
On a fresh install of the 4.0.4 ISO (omarchy 4.0.4-1, quickshell 0.3.1, Hyprland 0.56.2), with a terminal focused:
kill -SEGV "$(pgrep -n -x quickshell)" # stands in for a shell crash
hyprctl -j activewindow | jq .class # "org.quickshell": the dialog has focusThe core dump is in coredumpctl, and Quickshell writes its own report under ~/.cache/quickshell/crashes/. quattro (81145eb1) launches the shell the same way, and no window rule covers the dialog.
View raw text
### System details
Omarchy 4.0.4 (quickshell 0.3.1, Hyprland 0.56.2), fresh install in a VM
### What's wrong?
When the Omarchy shell crashes, Quickshell's own crash reporter opens a dialog ("Quickshell has crashed. Please submit a bug report…", class `org.quickshell`). It takes keyboard focus like any new window, even though the shell is already running again by then. Below 10 s of uptime, `omarchy-launch-shell` relaunches it; past that, Quickshell restarts itself.
So the dialog reports a crash that has already been handled, and it steals focus while doing so. The first button, "Open report page", is the highlighted one, so a Return typed just after the crash (mid-command in a terminal, for example) opens a browser on Quickshell's issue tracker. The crash also reaches Omarchy's own tooling: systemd-coredump records it, and `omarchy-crash-watch` offers a diagnosis.
#### Reproduce
On a fresh install of the 4.0.4 ISO (omarchy 4.0.4-1, quickshell 0.3.1, Hyprland 0.56.2), with a terminal focused:
```bash
kill -SEGV "$(pgrep -n -x quickshell)" # stands in for a shell crash
hyprctl -j activewindow | jq .class # "org.quickshell": the dialog has focus
```
The core dump is in `coredumpctl`, and Quickshell writes its own report under `~/.cache/quickshell/crashes/`. `quattro` (81145eb1) launches the shell the same way, and no window rule covers the dialog.
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 21:37 UTC