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.
Upgrades to users' installed elephant plugins conflict with Omarchy's repo's elephant version
Reported by marcoscannabrava · filed Dec 6, 2025Closed upstream on 2025-12-08. 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.2.2
What's wrong?
- If a user installs a custom elephant provider (e.g. elephant-windows to build an app switcher);
- And Omarchy's repo version of elephant (currently omarchy/elephant == 2.16.1) is outdated compared to the plugin (currently aur/elephant-windows == 2.17.0)
Then, because the Go version used to build the plugin will differ from the Go bin used to build elephant, the elephant provider will stop working — the user will see "Waiting for elephant". This can be verified by running elephant --debug.
My fix was to manually build the plugin I needed (elephant-windows) with the system's Go version.
Is there any better workaround than this?
Is it necessary to maintain the elephant pkg in the omarchy repo? Simply removing it from there should prevent the issue, I believe, since the maintainer of the elephant-* pkgs keeps them in sync.
Related: https://github.com/basecamp/omarchy/discussions/3778
View raw text
### System details Omarchy 3.2.2 ### What's wrong? 1. If a user installs a custom elephant provider (e.g. elephant-windows to build an app switcher); 2. And Omarchy's repo version of elephant (currently omarchy/elephant == 2.16.1) is outdated compared to the plugin (currently aur/elephant-windows == 2.17.0) Then, because the Go version used to build the plugin will differ from the Go bin used to build elephant, the elephant provider will stop working — the user will see "Waiting for elephant". This can be verified by running `elephant --debug`. My fix was to manually build the plugin I needed (elephant-windows) with the system's Go version. Is there any better workaround than this? Is it necessary to maintain the elephant pkg in the omarchy repo? Simply removing it from there should prevent the issue, I believe, since the maintainer of the elephant-* pkgs keeps them in sync. Related: https://github.com/basecamp/omarchy/discussions/3778
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.