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.
invokeLast IPC returns "none" instead of re-showing the last notification when no toast is on screen
Reported by erichsson · filed Aug 16, 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
The SUPER + ALT + comma keybinding ("Invoke last notification", bound toomarchy-shell notifications invokeLast) does nothing and prints none
whenever no notification toast is currently on screen — which is the normal
state, since toasts auto-expire after a few seconds.
What was expected
The most recent notification is re-shown as a toast — like showHistory
replays history, but for the newest entry only — so it can be seen (and its
action invoked) again.
Steps to reproduce
- Send a notification (e.g.
notify-send test), let the toast expire or
dismiss it.
2. Press SUPER + ALT + comma.
3. Nothing appears; omarchy-shell notifications invokeLast prints none.
Verified live: with 10 archived notifications in~/.local/state/omarchy/notifications/history/ and no popup on screen, the IPC
returns none.
Cause
shell/plugins/notifications/Service.qml, in the notifications IPC handler:
// Fire the default action on the most recent popup, then dismiss it.
function invokeLast(): string {
if (popupModel.count === 0) return "none"
service.invokePopupDefault(0)
return "ok"
}The guard on popupModel.count === 0 bails out instead of falling back to the
newest entry in historyDir — the same files showRecentHistory() replays.
System
- Omarchy 4.0.0-1 (stable)
- CPU: AMD Ryzen 5 5600X 6-Core Processor
- GPU: AMD Radeon RX 7600 (Navi 33)
View raw text
## What happened
The `SUPER + ALT + comma` keybinding ("Invoke last notification", bound to
`omarchy-shell notifications invokeLast`) does nothing and prints `none`
whenever no notification toast is currently on screen — which is the normal
state, since toasts auto-expire after a few seconds.
## What was expected
The most recent notification is re-shown as a toast — like `showHistory`
replays history, but for the newest entry only — so it can be seen (and its
action invoked) again.
## Steps to reproduce
1. Send a notification (e.g. `notify-send test`), let the toast expire or
dismiss it.
2. Press `SUPER + ALT + comma`.
3. Nothing appears; `omarchy-shell notifications invokeLast` prints `none`.
Verified live: with 10 archived notifications in
`~/.local/state/omarchy/notifications/history/` and no popup on screen, the IPC
returns `none`.
## Cause
`shell/plugins/notifications/Service.qml`, in the `notifications` IPC handler:
```qml
// Fire the default action on the most recent popup, then dismiss it.
function invokeLast(): string {
if (popupModel.count === 0) return "none"
service.invokePopupDefault(0)
return "ok"
}
```
The guard on `popupModel.count === 0` bails out instead of falling back to the
newest entry in `historyDir` — the same files `showRecentHistory()` replays.
## System
- Omarchy 4.0.0-1 (stable)
- CPU: AMD Ryzen 5 5600X 6-Core Processor
- GPU: AMD Radeon RX 7600 (Navi 33)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 04:27 UTC