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.
Proposal: Improve Theming Stability by Decoupling `walker` and `elephant` Restarts
Reported by MematiBas42 · filed Oct 20, 2025Closed upstream on 2025-10-21 by its own reporter MematiBas42. 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
What's wrong?
Hello Omarchy Team,
First, thank you for creating such a powerful and well-designed system. I've been implementing a dynamic theming solution using pywal and have
discovered an opportunity to make the entire theming process more robust and stable for everyone.
The Challenge:
For dynamic themes to apply correctly, UI components need to be reloaded. The omarchy-restart-walker script is used for this purpose. Currently, this
script restarts both walker and its helper service, elephant.
Under certain conditions, particularly the rapid reloads that occur during theme switching, the elephant service can become unstable and crash. This
appears to be due to an internal race condition in elephant's clipboard provider. When this happens, it disrupts the entire theme update flow.
Evidence (The elephant Crash Log):
1 fatal error: concurrent map read and map write
2
3 goroutine 99 [running]:
4 internal/runtime/maps.fatal({0x7f36cf749d3f?, 0xc0005b81c0?})
5 ...
6 github.com/abenz1267/elephant/v2/internal/providers/clipboard.updateText()
7 ...
The Solution Proposal:
I propose that we make the system more modular and resilient by decoupling the restart logic. The omarchy-restart-walker script's responsibility should
be narrowed to only restarting walker.
The elephant service can continue to run persistently in the background. Since walker only depends on elephant running (not on it being restarted
simultaneously), there is no need to restart elephant every time walker's theme is updated.
Proposed Implementation:
Modify the omarchy-restart-walker script to remove the lines related to elephant.
Current Script:
1 #!/bin/bash
2
3 pkill elephant
4 pkill walker
5
6 # ... (logic to restart both elephant and walker)
Proposed (More Robust) Script:
1 #!/bin/bash
2
3 pkill walker
4
5 # ... (logic to restart only walker --gapplication-service)
Benefits of this Change:
1. Increased Stability: Prevents a race condition in elephant from crashing the theming process.
2. Improved Modularity: Each service (walker, elephant) can be managed independently, adhering to the "do one thing and do it well" principle.
3. Better Theming Experience: Allows for seamless and reliable dynamic theme updates (e.g., with pywal) without any risk of instability.
This small change would improve the robustness of the entire Omarchy ecosystem for any user interested in dynamic theming. Thank you for your
consideration!
View raw text
### System details
omarchy
### What's wrong?
Hello Omarchy Team,
First, thank you for creating such a powerful and well-designed system. I've been implementing a dynamic theming solution using pywal and have
discovered an opportunity to make the entire theming process more robust and stable for everyone.
The Challenge:
For dynamic themes to apply correctly, UI components need to be reloaded. The omarchy-restart-walker script is used for this purpose. Currently, this
script restarts both walker and its helper service, elephant.
Under certain conditions, particularly the rapid reloads that occur during theme switching, the elephant service can become unstable and crash. This
appears to be due to an internal race condition in elephant's clipboard provider. When this happens, it disrupts the entire theme update flow.
Evidence (The `elephant` Crash Log):
1 fatal error: concurrent map read and map write
2
3 goroutine 99 [running]:
4 internal/runtime/maps.fatal({0x7f36cf749d3f?, 0xc0005b81c0?})
5 ...
6 github.com/abenz1267/elephant/v2/internal/providers/clipboard.updateText()
7 ...
The Solution Proposal:
I propose that we make the system more modular and resilient by decoupling the restart logic. The omarchy-restart-walker script's responsibility should
be narrowed to only restarting walker.
The elephant service can continue to run persistently in the background. Since walker only depends on elephant running (not on it being restarted
simultaneously), there is no need to restart elephant every time walker's theme is updated.
Proposed Implementation:
Modify the omarchy-restart-walker script to remove the lines related to elephant.
Current Script:
1 #!/bin/bash
2
3 pkill elephant
4 pkill walker
5
6 # ... (logic to restart both elephant and walker)
Proposed (More Robust) Script:
1 #!/bin/bash
2
3 pkill walker
4
5 # ... (logic to restart only walker --gapplication-service)
Benefits of this Change:
1. Increased Stability: Prevents a race condition in elephant from crashing the theming process.
2. Improved Modularity: Each service (walker, elephant) can be managed independently, adhering to the "do one thing and do it well" principle.
3. Better Theming Experience: Allows for seamless and reliable dynamic theme updates (e.g., with pywal) without any risk of instability.
This small change would improve the robustness of the entire Omarchy ecosystem for any user interested in dynamic theming. Thank you for your
consideration!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.