Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-4972GitHub issuePublicReceived

omarchy toggle bar: on/off arguments are inverted

Reported by fubartutu · filed Sep 9, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #7022 (R-1817). GitHub close reason: completed.

Received and recorded verbatim. Nothing has been checked yet.

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

omarchy toggle bar: on/off arguments are invertedrevision 1 · captured 2026-10-04 12:10 UTC via poll

What happened

omarchy toggle bar on hides the top bar, and omarchy toggle bar off shows it — the arguments are inverted relative to what the command name implies.

Expected

omarchy toggle bar on should show the bar; omarchy toggle bar off should hide it.

Steps to reproduce

omarchy toggle bar on   # bar disappears
omarchy toggle bar off  # bar reappears

Root cause

/usr/share/omarchy/bin/omarchy-toggle-bar forwards the raw on/off argument straight through to the generic toggle helper against a flag named bar-off, without inverting it:

#!/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-shell -q omarchy.bar syncHidden

omarchy-toggle <flag> on creates the flag file and ... off removes it. Since the flag here is named bar-off, passing on creates bar-off (hides the bar) and passing off removes it (shows the bar) — the opposite of the documented/expected behavior.

Fix is presumably to swap the mapping, e.g.:

case "${1:-toggle}" in
  on)     omarchy-toggle bar-off off ;;
  off)    omarchy-toggle bar-off on ;;
  *)      omarchy-toggle bar-off toggle ;;
esac

How I found this

The bar-off state flag also got left set after a theme change on my system (separate issue, possibly a race — the flag existed with a timestamp matching my omarchy theme set call), which caused the bar to disappear. While fixing that I ran omarchy toggle bar on expecting it to restore the bar, and it instead confirmed the flag (~/.local/state/omarchy/toggles/bar-off) stayed/got set. Running omarchy toggle bar off correctly cleared the flag and the bar layer (hyprctl layers) moved back from xywh: 0 -26 1800 26 to xywh: 0 0 1800 26.

System details

  • Omarchy version: 4.0.2-1
  • Compositor: Hyprland (Wayland)
View raw text
## What happened

`omarchy toggle bar on` hides the top bar, and `omarchy toggle bar off` shows it — the arguments are inverted relative to what the command name implies.

## Expected

`omarchy toggle bar on` should show the bar; `omarchy toggle bar off` should hide it.

## Steps to reproduce

```bash
omarchy toggle bar on   # bar disappears
omarchy toggle bar off  # bar reappears
```

## Root cause

`/usr/share/omarchy/bin/omarchy-toggle-bar` forwards the raw `on`/`off` argument straight through to the generic toggle helper against a flag named `bar-off`, without inverting it:

```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-shell -q omarchy.bar syncHidden
```

`omarchy-toggle <flag> on` *creates* the flag file and `... off` *removes* it. Since the flag here is named `bar-off`, passing `on` creates `bar-off` (hides the bar) and passing `off` removes it (shows the bar) — the opposite of the documented/expected behavior.

Fix is presumably to swap the mapping, 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
```

## How I found this

The `bar-off` state flag also got left set after a theme change on my system (separate issue, possibly a race — the flag existed with a timestamp matching my `omarchy theme set` call), which caused the bar to disappear. While fixing that I ran `omarchy toggle bar on` expecting it to restore the bar, and it instead confirmed the flag (`~/.local/state/omarchy/toggles/bar-off`) stayed/got set. Running `omarchy toggle bar off` correctly cleared the flag and the bar layer (`hyprctl layers`) moved back from `xywh: 0 -26 1800 26` to `xywh: 0 0 1800 26`.

## System details

- Omarchy version: 4.0.2-1
- Compositor: Hyprland (Wayland)

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.