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.
Configs broken after reverting to pre-update Snapshot
Reported by Varantha · filed May 20, 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
System details
Omarchy v3.8.0
What's wrong?
Problem
After an update to v3.8.0 went wrong, I tried to roll back to a Limine Snapshot that was created before the update. It rolled back the files but due to the change from .conf to .lua configs, my hyprland was broken / not as it should have been.
I tried to run omarchy reinstall configs to pull the default configs to get everything working again but that pulled the v3.8.0 configs again which didn't work with the version of Hyprland I had.
Root Cause
Snapshots only backup /root and not /home.
Default configs are stored in ~/.local/share/omarchy/config/ so the configs backups will stick to the new version
In the case that configs are refactored in a way that they become incompatible with an old version, reverting to a snapshot could break your configs
Possible Fix
There's maybe a wider question around how to manage rollbacks when migrations have happened to /home files between versions.
Perhaps if an update is known to be applying high-risk migrations, a second (short-lived) snapshot could be taken that targets home as well and users could choose to do a "Full" rollback if they needed. (Though I'm not sure how this would work with Limine)
But at the very least it would be good for the omarchy commands to help get things back to normal after a rollback if needed.
It's possible that ~/.local/share/omarchy/bin/ could be moved somewhere inside of /root so that it reverts to the older version with all the updated packages.
Or some command to rollback the Omarchy command center version could be useful. (Sorry if this already exists, I can't find one)
View raw text
### System details Omarchy v3.8.0 ### What's wrong? ## Problem After an update to v3.8.0 went wrong, I tried to roll back to a Limine Snapshot that was created before the update. It rolled back the files but due to the change from `.conf` to `.lua` configs, my hyprland was broken / not as it should have been. I tried to run `omarchy reinstall configs` to pull the default configs to get everything working again but that pulled the v3.8.0 configs again which didn't work with the version of Hyprland I had. ## Root Cause Snapshots only backup `/root` and not `/home`. Default configs are stored in `~/.local/share/omarchy/config/` so the configs backups will stick to the new version In the case that configs are refactored in a way that they become incompatible with an old version, reverting to a snapshot could break your configs ## Possible Fix There's maybe a wider question around how to manage rollbacks when migrations have happened to `/home` files between versions. Perhaps if an update is known to be applying high-risk migrations, a second (short-lived) snapshot could be taken that targets home as well and users could choose to do a "Full" rollback if they needed. (Though I'm not sure how this would work with Limine) But at the very least it would be good for the omarchy commands to help get things back to normal after a rollback if needed. It's possible that ` ~/.local/share/omarchy/bin/` could be moved somewhere inside of `/root` so that it reverts to the older version with all the updated packages. Or some command to rollback the Omarchy command center version could be useful. (Sorry if this already exists, I can't find one)
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.
- Out of scopeDecided by agents · verified · 2026-10-09 03:48 UTC