Proof Portal
Omarchy
ProbeLabsviewing a historical runA 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.
pendingInitialMenu is stored and never read: a route summoned before the JSONC loads opens root and stays there
This defect has been fixed and verified.
What this means for you
Plain-language impact — what this issue could mean for your users and your system, before any of the technical detail.
A menu key pressed while the shell is starting opens the main menu instead of the menu you asked for. This happens right after login, or after omarchy-restart-shell, which omarchy update runs. An action shortcut such as Super+Ctrl+R also opens the main menu, and its action never runs. Pressing it again a second later works.
Technical description
The shell queues a summon that arrives before the menu plugin loads. It hands the summon to open() as soon as the plugin loads. Neither menu FileView has read its JSONC file then, and the user extension usually answers first. So openRoute cannot resolve the route, and openExistingMenu falls back to root.
On 821ae589 nothing opens the route when the files land. openRoute writes the route to pendingInitialMenu, but nothing reads that property. The reader went away with the bash menu's replay (edfd68d4, 4cd6593b). A summon during startup (Super+Escape right after login or a shell restart) shows the main menu. An action alias such as reminder-set never runs. Seen live on 821ae589 in every cold-start run.
Affected requirements
The requirement(s) this issue violates — click through to the spec.
Severity, explained
Why this is rated the way it is — and the scoring signals behind the rating (each ⓘ explains the term).
- why this rating
- Risk-rated
- risk area
- Correctness
- CVE surface
- None
How it's proven
The reproducer — an actual test that drives the real code and shows the issue happening. Run it yourself, or peek the test and the source it covers.
known_issue_reproducerbash test/shell.d/menu-startup-route-test.sh
Reproduction steps
Technical steps for your engineers to confirm the issue by hand.
bash test/shell.d/menu-startup-route-test.sh
What protects you, and the fix
What limits your exposure today, and the planned remediation.
What protects you now
The race needs a summon landing before the JSONC loads (a sub-second window at session start); reopening lands on the intended route
The fix
Fixed upstream on #14055 (SW-REQ-261002-DK0D). A route that fell back to root stays pending until both menu files have answered. Then the menu tries it one time and drops it. Typing or opening another menu drops it earlier.
Blast radius
If you touch this issue, what else may need re-checking — the requirements it affects and the code and tests that hang off them. Historical view: authored trace links only — automatically derived links aren't reconstructible for past runs.
No authoredcode links reach these requirements in this historical reconstruction. Automatically derived code links aren't reconstructible for past runs, so implementing code may have existed without an authored trace.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
Evidence trail
The raw evidence manifests behind this finding — superseded by the resolved reproducer above, kept here for traceability.
- proof/evidence/ki-menu-pending-initial-menu-dead.yaml
- test/shell.d/menu-startup-route-test.sh
Change history
Every recorded revision of this finding's source file — when it was added, edited, or re-classified, with the diff for each change.
Discussions
Discuss this with the proof team. Nothing changes in your audit automatically — you open a request and a staff member records any outcome inside the thread.