Bring the bar back when omarchy update ends with no shell running
Re-read omarchy-restart-shell, omarchy-launch-shell and omarchy-update-restart on 4.0.4-1: while timeout 5 quickshell kill ..., launch via hyprctl dispatch 'hl.dsp.exec_cmd("omarchy-launch-shell")', quickshell -n, (( status == 0 )) && exit 0, the 20-attempt ping loop at 0.5 s IPC timeout, and omarchy-restart-shell || true all hold. quickshell list -p /usr/share/omarchy/shell prints one Instance ...: block here, so the grep count works. Two defects. The verify step still says quickshell list --all shows exactly one instance, which the first audit found false (other Quickshell configs are listed) and corrected only in the fix, so the verify contradicts the fix. And the cause is stale: #14085 and #14013 were closed on 2026-10-04 as fixed on quattro by PR #11015 (merged 2026-10-04), and quattro's restart-shell now uses timeout 30. The latest release is still v4.0.4, so stable is still affected. Cause updated to say so, verify corrected. The restart was not exercised.
Never run omarchy restart shell over ssh or while the session is locked. On a locked session it re-locks and waits for the lock to come back, and Omarchy 4's lock screen cannot be released headlessly. omarchy refresh shell overwrites ~/.config/omarchy/shell.json.
Symptom
omarchy update reports success, prints Restarting shell and All plugins have been reloaded, and then the bar is gone. Super+Space and every menu keybinding do nothing, notifications stop, but Hyprland and windows work. The supervisor logged no relaunching or Giving up line. The user journal shows a 5 to 6 second gap and then a refusal:
omarchy-shell[931]: INFO: Exiting due to IPC request.
omarchy-shell[3248]: An instance of this configuration is already running.
Running omarchy restart shell by hand may print Omarchy shell did not become ready after restart. and exit 1 even though the bar appears a few seconds later.
Cause
omarchy-update-restart ends with omarchy-restart-shell || true. On 4.0.4-1 that script runs while timeout 5 quickshell kill -p "$CONFIG_DIR" --any-display; do :; done and then launches omarchy-launch-shell. When the old shell takes more than 5 seconds to tear down, which is common right after an update has replaced its QML, timeout ends the wait, the loop exits, and the replacement quickshell -n (no-duplicate) sees the dying instance still registered and exits 0. omarchy-launch-shell treats exit 0 as a deliberate stop ((( status == 0 )) && exit 0), so nothing relaunches, and || true hides the failure from the update. Separately, the restart's readiness poll is 20 attempts at 0.1 s with a 0.5 s IPC timeout, about 2 seconds when no shell is listening yet, while a cold start measured 5 to 6 seconds on slow hardware, hence the false did not become ready. Both loops confirmed in the 4.0.4-1 scripts on this workstation. This is a different failure from the crash loop where the supervisor gives up after 6 relaunches. Upstream fixed both on quattro in PR #11015, merged 2026-10-04, which per its closing comment waits up to 30 seconds for the old shell, checks that its instance has gone, and allows 60 seconds for readiness. As of 2026-10-05 the latest release is still v4.0.4, so stable installs keep the race until a newer release ships.
Fix
From a terminal in your unlocked desktop session:
omarchy restart shell
If it prints Omarchy shell did not become ready after restart., wait about ten seconds before doing anything else, then check rather than re-running it:
OMARCHY_SHELL_IPC_TIMEOUT=10s omarchy-shell shell ping # expect: ok
hyprctl layers | grep omarchy-bar
quickshell list -p /usr/share/omarchy/shell | grep -c '^Instance' # expect: 1
Do not use quickshell list --all for that count: it also lists Quickshell instances of other configs.
To confirm this was the restart race and not a crash:
journalctl --user -b -t omarchy-shell --no-pager | grep -E 'Exiting due to IPC|already running|relaunching|Giving up'
Exiting due to IPC request followed within seconds by already running, with no relaunching line, is this problem.
Use omarchy restart shell, not omarchy refresh shell: the refresh resets ~/.config/omarchy/shell.json to defaults and throws away a customised bar layout.
Verify
omarchy-shell shell ping prints ok, hyprctl layers lists the omarchy-bar namespace, quickshell list -p /usr/share/omarchy/shell | grep -c '^Instance' prints 1, and Super+Space opens the menu.