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.
Can't open defaults anymore if the editor set is broken
Reported by devzeth · filed Sep 26, 2025Closed upstream on 2025-11-26 by its own reporter devzeth. GitHub close reason: completed. Closed by its own reporter — not by itself 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.0.1
What's wrong?
- Setup > Defaults, change the editor to zed for example ( its what I tried to do and broke it)
- Now press super N, it should open zed
- For some reason it doesn't find it, and there is no fallback.
If we now go back to Setup > Defaults, we are stuck. It doesn't find zed, and there is no fallback. Its then up to the user if he is smart enough to go tinker and find out where to fix it.
View raw text
### System details Omarchy 3.0.1 ### What's wrong? 1. Setup > Defaults, change the editor to zed for example ( its what I tried to do and broke it) 2. Now press super N, it should open zed 3. For some reason it doesn't find it, and there is no fallback. If we now go back to Setup > Defaults, we are stuck. It doesn't find zed, and there is no fallback. Its then up to the user if he is smart enough to go tinker and find out where to fix it.
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.