Proof Portal

Sign in
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-3243GitHub issuePublicReceived

Waybar proposal: only restart waybar if its already running when switching themes

Reported by celsobenedetti · filed Oct 9, 2025Closed upstream on 2025-10-13 by its own reporter celsobenedetti. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Open at source
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

Waybar proposal: only restart waybar if its already running when switching themesrevision 1 · captured 2026-10-04 11:42 UTC via poll

What do you need?

the issue

If we have Waybar toggled off (super+shift+space), and then switch themes (omarchy-set-theme), waybar will be spawned here.

I'd argue the UX is not ideal: if the user had waybar off, we should trust they meant it.

proposal

when switching theme:
only run omarchy-restart-waybar if pgrep waybar

something like:

diff --git a/bin/omarchy-theme-set b/bin/omarchy-theme-set
index 7305971..6e80bf6 100755
--- a/bin/omarchy-theme-set
+++ b/bin/omarchy-theme-set
@@ -24,7 +24,9 @@ ln -nsf "$THEME_PATH" "$CURRENT_THEME_DIR"
 omarchy-theme-bg-next
 
 # Restart components to apply new theme
-omarchy-restart-waybar
+if pgrep -x waybar >/dev/null; then
+    omarchy-restart-waybar
+fi
 omarchy-restart-swayosd
 hyprctl reload
 pkill -SIGUSR2 btop

Thank you! 🙂

View raw text
### What do you need?

### the issue

If we have Waybar toggled off (`super+shift+space`), and then switch themes (`omarchy-set-theme`), waybar will be spawned [here](https://github.com/basecamp/omarchy/blob/master/bin/omarchy-theme-set#L27-L27).

I'd argue the UX is not ideal: if the user had waybar off, we should trust they meant it.

### proposal

when switching theme:
only run `omarchy-restart-waybar` if `pgrep waybar`

something like:

```diff
diff --git a/bin/omarchy-theme-set b/bin/omarchy-theme-set
index 7305971..6e80bf6 100755
--- a/bin/omarchy-theme-set
+++ b/bin/omarchy-theme-set
@@ -24,7 +24,9 @@ ln -nsf "$THEME_PATH" "$CURRENT_THEME_DIR"
 omarchy-theme-bg-next
 
 # Restart components to apply new theme
-omarchy-restart-waybar
+if pgrep -x waybar >/dev/null; then
+    omarchy-restart-waybar
+fi
 omarchy-restart-swayosd
 hyprctl reload
 pkill -SIGUSR2 btop
```

Thank you! 🙂

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.