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.
Shell restores unbounded backlog of stale never-expiring critical popups after power loss (plus 0-byte state files)
Reported by calumol · filed Sep 1, 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
My laptop ran its battery flat and powered off with ~260 undismissed critical "Time to recharge!" popups on screen (the storm itself is a separate bug — see #9670). On the next boot, the shell rehydrated the entire backlog from `~/.local/state/omarchy/notifications/` and displayed a full-screen wall of stale "Battery is down to 3%" toasts — from a session that had ended two hours earlier, while the battery was by then happily charging.
Because they're critical urgency, durationFor() returns 0 and none of them ever auto-expire; they sit there until each is manually dismissed (or omarchy notification dismiss "Time to recharge!").
The abrupt power-off also left 11 zero-byte popup state files (writes truncated at the moment of death):
-rw-r--r-- 1 calum calum 0 Sep 1 14:27 1788287246194-307.json
-rw-r--r-- 1 calum calum 0 Sep 1 14:27 1788287249390-308.json
...These hydrated as blank/summary-less popups, and since omarchy notification dismiss matches on summary substring, there was no way to dismiss them by summary — I had to delete the files by hand.
Expected
Popup persistence surviving a shell restart is a nice feature, but restore should be bounded:
- Cap the hydrated backlog by count and/or age (e.g. don't restore popups older than a few minutes, or more than ~10 — anything beyond that belongs in history, which is already capped at
historyLimit). - Coalesce duplicates on restore (same app + summary + body) into one popup.
- Discard empty/unparsable state files during hydration instead of surfacing blank toasts.
System
- Framework Laptop 13 (AMD Ryzen 7 7840HS / Radeon 780M)
- Omarchy
4.0.0.r1846.g946704f-1, quickshell0.3.1-1, kernel7.1.9-arch1-2
Related: #9361 (critical toasts never auto-expire, which is why the backlog can only grow).
View raw text
## What happened My laptop ran its battery flat and powered off with ~260 undismissed critical "Time to recharge!" popups on screen (the storm itself is a separate bug — see #9670). On the next boot, the shell **rehydrated the entire backlog from `~/.local/state/omarchy/notifications/` and displayed a full-screen wall of stale "Battery is down to 3%" toasts** — from a session that had ended two hours earlier, while the battery was by then happily charging. Because they're critical urgency, `durationFor()` returns `0` and none of them ever auto-expire; they sit there until each is manually dismissed (or `omarchy notification dismiss "Time to recharge!"`). The abrupt power-off also left **11 zero-byte popup state files** (writes truncated at the moment of death): ``` -rw-r--r-- 1 calum calum 0 Sep 1 14:27 1788287246194-307.json -rw-r--r-- 1 calum calum 0 Sep 1 14:27 1788287249390-308.json ... ``` These hydrated as blank/summary-less popups, and since `omarchy notification dismiss` matches on summary substring, there was no way to dismiss them by summary — I had to delete the files by hand. ## Expected Popup persistence surviving a shell restart is a nice feature, but restore should be bounded: - **Cap the hydrated backlog** by count and/or age (e.g. don't restore popups older than a few minutes, or more than ~10 — anything beyond that belongs in history, which is already capped at `historyLimit`). - **Coalesce duplicates on restore** (same app + summary + body) into one popup. - **Discard empty/unparsable state files** during hydration instead of surfacing blank toasts. ## System - Framework Laptop 13 (AMD Ryzen 7 7840HS / Radeon 780M) - Omarchy `4.0.0.r1846.g946704f-1`, quickshell `0.3.1-1`, kernel `7.1.9-arch1-2` Related: #9361 (critical toasts never auto-expire, which is why the backlog can only grow).
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/9790· 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 10:29 UTC