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 arguments are inverted
Reported by macbe · filed Sep 7, 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
What happened
omarchy toggle bar on hides the bar, and omarchy toggle bar off shows it — the opposite of what the command's own help text (omarchy toggle bar [toggle|on|off]) promises.
Why
bin/omarchy-toggle-bar forwards its argument as-is to the generic toggle helper, but the underlying flag is named bar-off (negated), not bar:
#!/bin/bash
# omarchy:summary=Toggle bar visibility without killing the Omarchy shell
# omarchy:args=[toggle|on|off]
# omarchy:examples=omarchy toggle bar | omarchy toggle bar off | omarchy toggle bar on
omarchy-toggle bar-off "${1:-toggle}"omarchy-toggle (the shared helper) just does enable/disable on ~/.local/state/omarchy/toggles/<flag-name> based on the literal on/off argument:
case "$ACTION" in
...
on)
enable
;;
off)
disable
;;So omarchy toggle bar on → omarchy-toggle bar-off on → enables bar-off → bar hidden. And omarchy toggle bar off → disables bar-off → bar shown. Bare omarchy toggle bar (no argument) is unaffected since it just flips whichever state currently exists.
Expected
omarchy toggle bar on should show the bar, omarchy toggle bar off should hide it.
Fix
omarchy-toggle-bar should invert the argument before forwarding it to the negated bar-off flag, e.g.:
case "${1:-toggle}" in
on) omarchy-toggle bar-off off ;;
off) omarchy-toggle bar-off on ;;
*) omarchy-toggle bar-off toggle ;;
esacSteps to reproduce
omarchy toggle bar off # bar disappears... but this is "off" so seems correct
omarchy toggle bar on # bar stays hidden — should have reappearedConfirmed via hyprctl layers: with the bar-off flag present, the bar's layer surface still exists but is rendered at y = -26 (pushed entirely above the top edge of a 26px-tall bar), rather than being destroyed — so the effect is a bar that looks "gone" rather than an obvious toggle state.
Side effect for end users
Because the flag lives in ~/.local/state/omarchy/toggles/bar-off (not a config file), an accidental bar-off toggle (e.g. a stray keybind) persists across reboots and Omarchy shell restarts, which reads as "my bar disappeared and won't come back" rather than "I toggled it off." Worth a note in the FAQs but the argument-inversion is the actual bug.
System details
- Omarchy version: 4.0.2-1
- Compositor: Hyprland 0.56.2
- Laptop: Lenovo Legion Y530-15ICH-1060, Intel UHD 630 + NVIDIA GTX 1060 (nvidia driver 580.178.04)
Diagnostic log
Generated via omarchy debug --no-sudo --print; happy to attach the full log on request (trimmed here since it's mostly unrelated hardware/system info).
View raw text
## What happened
`omarchy toggle bar on` hides the bar, and `omarchy toggle bar off` shows it — the opposite of what the command's own help text (`omarchy toggle bar [toggle|on|off]`) promises.
## Why
`bin/omarchy-toggle-bar` forwards its argument as-is to the generic toggle helper, but the underlying flag is named `bar-off` (negated), not `bar`:
```bash
#!/bin/bash
# omarchy:summary=Toggle bar visibility without killing the Omarchy shell
# omarchy:args=[toggle|on|off]
# omarchy:examples=omarchy toggle bar | omarchy toggle bar off | omarchy toggle bar on
omarchy-toggle bar-off "${1:-toggle}"
```
`omarchy-toggle` (the shared helper) just does `enable`/`disable` on `~/.local/state/omarchy/toggles/<flag-name>` based on the literal `on`/`off` argument:
```bash
case "$ACTION" in
...
on)
enable
;;
off)
disable
;;
```
So `omarchy toggle bar on` → `omarchy-toggle bar-off on` → **enables** `bar-off` → bar hidden. And `omarchy toggle bar off` → **disables** `bar-off` → bar shown. Bare `omarchy toggle bar` (no argument) is unaffected since it just flips whichever state currently exists.
## Expected
`omarchy toggle bar on` should show the bar, `omarchy toggle bar off` should hide it.
## Fix
`omarchy-toggle-bar` should invert the argument before forwarding it to the negated `bar-off` flag, e.g.:
```bash
case "${1:-toggle}" in
on) omarchy-toggle bar-off off ;;
off) omarchy-toggle bar-off on ;;
*) omarchy-toggle bar-off toggle ;;
esac
```
## Steps to reproduce
```bash
omarchy toggle bar off # bar disappears... but this is "off" so seems correct
omarchy toggle bar on # bar stays hidden — should have reappeared
```
Confirmed via `hyprctl layers`: with the `bar-off` flag present, the bar's layer surface still exists but is rendered at `y = -26` (pushed entirely above the top edge of a 26px-tall bar), rather than being destroyed — so the effect is a bar that looks "gone" rather than an obvious toggle state.
## Side effect for end users
Because the flag lives in `~/.local/state/omarchy/toggles/bar-off` (not a config file), an accidental bar-off toggle (e.g. a stray keybind) persists across reboots and Omarchy shell restarts, which reads as "my bar disappeared and won't come back" rather than "I toggled it off." Worth a note in the FAQs but the argument-inversion is the actual bug.
## System details
- Omarchy version: 4.0.2-1
- Compositor: Hyprland 0.56.2
- Laptop: Lenovo Legion Y530-15ICH-1060, Intel UHD 630 + NVIDIA GTX 1060 (nvidia driver 580.178.04)
## Diagnostic log
Generated via `omarchy debug --no-sudo --print`; happy to attach the full log on request (trimmed here since it's mostly unrelated hardware/system info).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.