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.
Terminal Doesn't Launch(via Super+Enter) After Upgrading to Omarchy 3.1.5
Reported by jandrusk · filed Nov 6, 2025Closed upstream on 2025-11-09 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
Omarchy 3.1.5
What's wrong?
After upgrading to Omarchy 3.1.5 and hitting Super+Enter to launch a Terminal, nothing happens. Manually launching another terminal app and manually running, 'uwsm app -- $TERMINAL --working-directory $(omarchy-cmd-terminal-cwd)' produces the error "Error: Custom { kind: PermissionDenied, error: "Failed to spawn command '/home/jra': Permission denied (os error 13)"
Searched the web and found the solution here: https://search.brave.com/search?q=uwsm+app+--+%24TERMINAL+--working-directory+%24%28omarchy-cmd-terminal-cwd%29+produces+%22Error%3A+Custom+%7B+kind%3A+PermissionDenied%2C+error%3A+%22Failed+to+spawn+command+%27%2Fhome%2Fjra%27%3A+Permission+denied+%28os+error+13%29%22+%7D&summary=1&conversation=2c83e717bb81c2569e67e4
omarchy-update should be patched to fix this binding error in ~/.hypr/bindings.conf.
View raw text
### System details
Omarchy 3.1.5
### What's wrong?
After upgrading to Omarchy 3.1.5 and hitting Super+Enter to launch a Terminal, nothing happens. Manually launching another terminal app and manually running, 'uwsm app -- $TERMINAL --working-directory $(omarchy-cmd-terminal-cwd)' produces the error "Error: Custom { kind: PermissionDenied, error: "Failed to spawn command '/home/jra': Permission denied (os error 13)"
Searched the web and found the solution here: https://search.brave.com/search?q=uwsm+app+--+%24TERMINAL+--working-directory+%24%28omarchy-cmd-terminal-cwd%29+produces+%22Error%3A+Custom+%7B+kind%3A+PermissionDenied%2C+error%3A+%22Failed+to+spawn+command+%27%2Fhome%2Fjra%27%3A+Permission+denied+%28os+error+13%29%22+%7D&summary=1&conversation=2c83e717bb81c2569e67e4
omarchy-update should be patched to fix this binding error in ~/.hypr/bindings.conf.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.
No decision has been recorded yet.