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.
`omarchy toggle bar on/off` behaves in reverse
Reported by zieglerziga · filed Sep 5, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #7022 (R-1817). GitHub close reason: completed.
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
Steam Deck (AMD Custom APU 0405 / AMD VanGogh GPU), Omarchy 4.0.1-1, Quickshell 0.3.1-1, Hyprland 0.56.2-1.
What's wrong?
The explicit on and off actions of omarchy toggle bar behave in reverse.
Steps to reproduce:
- Ensure the Omarchy shell and bar are running.
- Run
omarchy toggle bar on. - Observe that the bar is hidden and
~/.local/state/omarchy/toggles/bar-offis created. - Run
omarchy toggle bar off. - Observe that the marker is removed and the bar is shown.
Expected behavior:
omarchy toggle bar onshows the bar.omarchy toggle bar offhides the bar.omarchy toggle barcontinues toggling the current state.
Actual behavior:
omarchy toggle bar onhides the bar.omarchy toggle bar offshows the bar.
The no-argument toggle action works. The inverted state persists across shell restarts and can become noticeable after monitor hotplug, when Quickshell recreates its per-monitor bar surface and reads the persisted bar-off marker.
Root cause:
bin/omarchy-toggle-bar forwards the user-facing action directly to a negatively named generic flag:
omarchy-toggle bar-off "${1:-toggle}"The generic helper implements on by creating its flag and off by removing it. Therefore, bar on creates bar-off, while bar off removes it.
A possible fix is to translate the explicit actions while leaving toggle unchanged:
case "${1:-toggle}" in
on) omarchy-toggle bar-off off ;;
off) omarchy-toggle bar-off on ;;
toggle) omarchy-toggle bar-off toggle ;;
*)
echo "Usage: omarchy toggle bar [toggle|on|off]" >&2
exit 1
;;
esacI reproduced and verified both directions locally. omarchy-debug --no-sudo --print completed successfully; the relevant package versions are included above.
View raw text
### System details
Steam Deck (AMD Custom APU 0405 / AMD VanGogh GPU), Omarchy 4.0.1-1, Quickshell 0.3.1-1, Hyprland 0.56.2-1.
### What's wrong?
The explicit `on` and `off` actions of `omarchy toggle bar` behave in reverse.
Steps to reproduce:
1. Ensure the Omarchy shell and bar are running.
2. Run `omarchy toggle bar on`.
3. Observe that the bar is hidden and `~/.local/state/omarchy/toggles/bar-off` is created.
4. Run `omarchy toggle bar off`.
5. Observe that the marker is removed and the bar is shown.
Expected behavior:
- `omarchy toggle bar on` shows the bar.
- `omarchy toggle bar off` hides the bar.
- `omarchy toggle bar` continues toggling the current state.
Actual behavior:
- `omarchy toggle bar on` hides the bar.
- `omarchy toggle bar off` shows the bar.
The no-argument toggle action works. The inverted state persists across shell restarts and can become noticeable after monitor hotplug, when Quickshell recreates its per-monitor bar surface and reads the persisted `bar-off` marker.
Root cause:
`bin/omarchy-toggle-bar` forwards the user-facing action directly to a negatively named generic flag:
```bash
omarchy-toggle bar-off "${1:-toggle}"
```
The generic helper implements `on` by creating its flag and `off` by removing it. Therefore, `bar on` creates `bar-off`, while `bar off` removes it.
A possible fix is to translate the explicit actions while leaving `toggle` unchanged:
```bash
case "${1:-toggle}" in
on) omarchy-toggle bar-off off ;;
off) omarchy-toggle bar-off on ;;
toggle) omarchy-toggle bar-off toggle ;;
*)
echo "Usage: omarchy toggle bar [toggle|on|off]" >&2
exit 1
;;
esac
```
I reproduced and verified both directions locally. `omarchy-debug --no-sudo --print` completed successfully; the relevant package versions are included above.
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.