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.
no themes after update
Reported by Donnxx · filed Apr 30, 2026Closed upstream on 2026-05-02 by its own reporter Donnxx. 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
Macbook Air 7, 2
What's wrong?
After running an omarchy update, elephant and walker were missing and needed to be reinstalled via yay -S elephant walker. After reinstalling, walker works for launching apps but elephant listproviders only returns desktopapplications — none of the menus (omarchy_themes, omarchy_background_selector, omarchy_unlocks) are loaded despite the symlinks in ~/.config/elephant/menus/ being intact and correct.
Result: The theme switcher in the system menu shows nothing, making it impossible to switch themes through the UI.
Workaround: Manually switch themes via terminal:omarchy-theme-set <theme-name>
What we checked:
Symlinks in ~/.config/elephant/menus/ are intact and point to the correct lua files
OMARCHY_PATH is correctly set to ~/.local/share/omarchy
elephant.service is running
The find command in omarchy_themes.lua correctly finds themes when run manually
Re-running elephant service enable and restarting the service did not resolve it
Expected behavior: After reinstalling elephant/walker, running the install script (walker-elephant.sh) or equivalent should fully restore menu providers including the theme switcher.
Possible cause: The reinstall/update process does not re-run the omarchy elephant config setup, leaving elephant without its menu providers.
this was a AI Summary i have no idea what im doing but im trying XD
Thank you in advance
View raw text
### System details Macbook Air 7, 2 ### What's wrong? After running an omarchy update, elephant and walker were missing and needed to be reinstalled via yay -S elephant walker. After reinstalling, walker works for launching apps but elephant listproviders only returns desktopapplications — none of the menus (omarchy_themes, omarchy_background_selector, omarchy_unlocks) are loaded despite the symlinks in ~/.config/elephant/menus/ being intact and correct. Result: The theme switcher in the system menu shows nothing, making it impossible to switch themes through the UI. Workaround: Manually switch themes via terminal: `omarchy-theme-set <theme-name>` What we checked: Symlinks in ~/.config/elephant/menus/ are intact and point to the correct lua files OMARCHY_PATH is correctly set to ~/.local/share/omarchy elephant.service is running The find command in omarchy_themes.lua correctly finds themes when run manually Re-running elephant service enable and restarting the service did not resolve it Expected behavior: After reinstalling elephant/walker, running the install script (walker-elephant.sh) or equivalent should fully restore menu providers including the theme switcher. Possible cause: The reinstall/update process does not re-run the omarchy elephant config setup, leaving elephant without its menu providers. this was a AI Summary i have no idea what im doing but im trying XD Thank you in advance
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.