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.
Updating Omarchy with custom configs will sometimes produce invalid configs
Reported by cairin · filed Oct 24, 2025Closed upstream on 2025-10-24 by its own reporter cairin. 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 upgrade from 3.1.1 -> 3.1.2
What's wrong?
I had some custom elements in waybar, the update from 3.1.1 -> 3.1.2 changed something that broke the waybar config, preventing it from rendering.
First prize would be to validate that the updated configs are valid, and alert the user if they're potentially broken. But even just a check to see if the config has been customized and alert the user that the update may have produced invalid configs would suffice.
View raw text
### System details Omarchy upgrade from 3.1.1 -> 3.1.2 ### What's wrong? I had some custom elements in waybar, the update from 3.1.1 -> 3.1.2 changed something that broke the waybar config, preventing it from rendering. First prize would be to validate that the updated configs are valid, and alert the user if they're potentially broken. But even just a check to see if the config has been customized and alert the user that the update may have produced invalid configs would suffice.
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.