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 has inverted semantics, can strand bar off-screen
Reported by SDLyle · filed Sep 14, 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 does not show the bar — it sets the internal bar-off state flag, which hides it. omarchy toggle bar off is what actually clears that flag and shows the bar. The command names are inverted from their documented behavior.
Separately (and how I found this): the bar can get stuck off-screen (layer surface rendered at y = -<bar height> instead of y = 0) after a toggle, because the shell's watch on the toggles directory can miss flag changes that land in quick succession — this is called out in a comment in omarchy-toggle-bar itself. Running omarchy toggle bar on (intending to restore it) did not fix this, because of the inverted semantics above; only removing the flag file directly and forcing a resync fixed it.
Expected
omarchy toggle bar onshows the bar;omarchy toggle bar offhides it (matching the documented examples inomarchy bar --help/omarchy commands --json).- The bar should reliably reflect the current toggle flag state without needing a manual
omarchy-shell -q omarchy.bar syncHiddenor a full shell restart.
Steps to reproduce
omarchy toggle bar off— bar hides (as expected).omarchy toggle bar on— bar stays hidden (unexpected; should show).- Inspect
hyprctl layers— theomarchy-barlayer surface is present but positioned off-screen (xywh: 0 -26 1920 26instead ofxywh: 0 0 1920 26). - Inspect
~/.local/state/omarchy/toggles/bar-off— the flag file exists even after step 2's "on".
Root cause (as far as I traced it)
omarchy-toggle-bar forwards its own on/off argument straight through to the underlying flag toggler:
omarchy-toggle bar-off "${1:-toggle}"Since the flag is named bar-off, passing on enables the bar-off flag (hiding the bar) and passing off disables it (showing the bar) — exactly backwards from the command's own name and its own --help examples (omarchy toggle bar off / omarchy toggle bar on).
Workaround used
rm -f ~/.local/state/omarchy/toggles/bar-off
omarchy-shell -q omarchy.bar syncHiddenSystem info
- Omarchy version: 4.0.2-1
- CPU: AMD Ryzen 7 7800X3D
- Multi-monitor setup (3 monitors: HDMI-A-1, DP-1, DP-3) — bar was affected identically on all three.
- Full diagnostic log:
/tmp/omarchy-debug.log(generated viaomarchy-debug --no-sudo --print)
🤖 Generated with Claude Code
View raw text
## What happened
`omarchy toggle bar on` does not show the bar — it sets the internal `bar-off` state flag, which hides it. `omarchy toggle bar off` is what actually clears that flag and shows the bar. The command names are inverted from their documented behavior.
Separately (and how I found this): the bar can get stuck off-screen (layer surface rendered at `y = -<bar height>` instead of `y = 0`) after a toggle, because the shell's watch on the toggles directory can miss flag changes that land in quick succession — this is called out in a comment in `omarchy-toggle-bar` itself. Running `omarchy toggle bar on` (intending to restore it) did not fix this, because of the inverted semantics above; only removing the flag file directly and forcing a resync fixed it.
## Expected
- `omarchy toggle bar on` shows the bar; `omarchy toggle bar off` hides it (matching the documented examples in `omarchy bar --help` / `omarchy commands --json`).
- The bar should reliably reflect the current toggle flag state without needing a manual `omarchy-shell -q omarchy.bar syncHidden` or a full shell restart.
## Steps to reproduce
1. `omarchy toggle bar off` — bar hides (as expected).
2. `omarchy toggle bar on` — bar stays hidden (unexpected; should show).
3. Inspect `hyprctl layers` — the `omarchy-bar` layer surface is present but positioned off-screen (`xywh: 0 -26 1920 26` instead of `xywh: 0 0 1920 26`).
4. Inspect `~/.local/state/omarchy/toggles/bar-off` — the flag file exists even after step 2's "on".
## Root cause (as far as I traced it)
`omarchy-toggle-bar` forwards its own `on`/`off` argument straight through to the underlying flag toggler:
```bash
omarchy-toggle bar-off "${1:-toggle}"
```
Since the flag is named `bar-off`, passing `on` *enables* the `bar-off` flag (hiding the bar) and passing `off` *disables* it (showing the bar) — exactly backwards from the command's own name and its own `--help` examples (`omarchy toggle bar off` / `omarchy toggle bar on`).
## Workaround used
```bash
rm -f ~/.local/state/omarchy/toggles/bar-off
omarchy-shell -q omarchy.bar syncHidden
```
## System info
- Omarchy version: 4.0.2-1
- CPU: AMD Ryzen 7 7800X3D
- Multi-monitor setup (3 monitors: HDMI-A-1, DP-1, DP-3) — bar was affected identically on all three.
- Full diagnostic log: `/tmp/omarchy-debug.log` (generated via `omarchy-debug --no-sudo --print`)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01KWF9rTD7F7dUmq6pwJe4xVValidation
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.