Top bar gone and staying gone: omarchy-shell crash-loops and its supervisor gives up
Re-read /usr/share/omarchy/bin/omarchy-launch-shell, omarchy-restart-shell, omarchy-refresh-config, omarchy-theme-set-templates and omarchy-update-restart on this workstation at omarchy 4.0.2-1, quickshell 0.3.1-1, hyprland 0.56.2-1, and re-read omacom/omarchy issues 7380 and 8647 in full. The first-pass audit note still holds on the supervisor: the budget is exactly if (( ++attempts > 5 )) inside a SECONDS - window_started > 60 window, both logger lines are verbatim, and the shell really is systemd-cat -t omarchy-shell -- quickshell -n -p "$OMARCHY_PATH/shell". Confirmed on this machine that the journal tag is live and current: journalctl --user -t omarchy-shell returns Quickshell's own WARN output, and hyprctl layers shows the omarchy-bar namespace the verify step names. Four things the note missed. First, omarchy-restart-shell on 4.0.2-1 no longer only refuses on a locked session: when omarchy-hyprland-session-locked is true but omarchy-shell lock status reports neither .secure nor .requested, it sets relock=1, restarts the shell, and then calls relock_session(), which requests a lock and polls up to 30 seconds, so the record's own step 2 can deliberately lock a session the reader is recovering over ssh or on a headless machine, and Omarchy 4's lock cannot be released headlessly. Second, ~/.cache/quickshell/crashes does not exist on this machine at all, and the launcher's own comment says the Wayland-fatal path leaves through _exit() raising no signal and therefore writing no crash report, so for the record's own lead trigger that directory is empty by design. Third, the record bisects plugins and shell.json but has no branch for a broken theme or template: omarchy-theme-set-templates globs $HOME/.config/omarchy/themed/*.tpl before the shipped templates and user templates win, so a broken user template writes a broken generated shell.toml into the staged theme that the shell then loads, and omarchy-refresh-config omarchy/shell.json does not touch it. Fourth, two supervisor exits are unmentioned and both change what the reader sees: compositor_alive || exit 0 takes three hyprctl -j monitors tries and then exits silently with no journal line at all, and the 60 second window resets attempts=0, so a shell dying slower than once a minute flaps forever and never logs the give-up line. Also cross-referenced: trigger (1) and trigger (3) are the version-mismatch case already covered by omarchy-shell-quickshell-undefined-symbol-qt-private-api, whose fix is omarchy update rather than the reboot at step 6, and issue 7380's own body says it self-heals in about a second, so it only produces this record's symptom when it fires six times inside a minute. NOT exercised: nothing was restarted, no theme command was run, no unit was touched, and /etc/sudoers.d/ is unreadable unprivileged so the passwordless rules were not inspected. The 22 shipped themes and the helper scripts were listed, not executed.
**omarchy-restart-shell can lock the session on you.** On 4.0.2-1 it only refuses when a locker is alive and reports the lock secure or in progress:
Refusing to restart Omarchy shell while the session is locked.
When the session is compositor-locked but the locker is dead, which is the common case after this crash, it does the opposite: it restarts the shell and then deliberately re-acquires the lock, polling up to 30 seconds until the session reports secure. Omarchy 4's lock screen is an ext-session-lock surface with no unlock() IPC, so on a headless or ssh-only machine you cannot get back out except by typing the password at the console or rebooting. Check with omarchy-hyprland-session-locked before you run it, and if you have no console, reboot instead.
Do not force past the refusal branch either. Killing a live locker leaves you behind Hyprland's failsafe with no way to authenticate.
If you move ~/.config/omarchy/plugins or ~/.config/omarchy/themed aside, move them back after testing. Saving a file under the plugins directory while the session is locked has itself been reported to strand the session (issue #7106).
Symptom
The Omarchy top bar disappears and does not come back. No tray icons, Super+Space does nothing, the theme and background switchers never render, notifications stop. hyprctl layers shows omarchy-background but no omarchy-bar. In the journal:
omarchy-shell[2888127]: Omarchy shell exited with status 255; relaunching.
omarchy-shell[…]: Giving up on the Omarchy shell after 6 relaunches in under a minute.
You will see five relaunching lines before that one. The supervisor increments to 6 and then refuses, so the sixth relaunch never happens.
There is a second, quieter shape of the same problem: the bar is gone and the journal says **nothing**. The supervisor checks the compositor before spending an attempt, and when hyprctl -j monitors fails three times it exits silently without logging. Do not read an empty journal as proof the shell never died.
Other fatal lines seen right before it dies:
WARN quickshell.hyprland.ipc: Got removal for monitor "FALLBACK" which was not previously tracked.
WARN: The Wayland connection experienced a fatal error: Invalid argument
FATAL: Tried to show lockscreen surfaces without active lock
quickshell: symbol lookup error: undefined symbol: … Qt_6_PRIVATE_API
Often Wi-Fi, Bluetooth or audio appear dead at the same time simply because their bar controls are gone.
Cause
Omarchy 4 dropped Waybar. The bar, tray, notifications, launcher, menu and lock screen are all one Quickshell process, omarchy-shell, launched and supervised by omarchy-launch-shell. That supervisor relaunches on a non-zero exit, but gives up once the failure count passes 5 inside a 60 second window:
if (( SECONDS - window_started > 60 )); then attempts=0; window_started=$SECONDS; fi
if (( ++attempts > 5 )); then
logger -t omarchy-shell "Giving up on the Omarchy shell after $attempts relaunches in under a minute."
exit 1
fi
Two consequences follow from that shape. The window resets, so a shell dying slower than once a minute never exhausts the budget and flaps forever instead of stopping. And a preceding compositor_alive || exit 0 makes the supervisor leave silently, with no log line, when hyprctl -j monitors fails three times, which is the case where the bar is gone and the journal is empty.
Four distinct triggers, with four different fixes. Tell them apart from the journal before acting.
- **A
quickshellor Qt upgrade landing while the old shell is still running.** Updates rewrite$OMARCHY_PATH/shell, andomarchy-update-restartrestarts the shell unconditionally for exactly this reason. If the journal carriesundefined symbol: … Qt_6_PRIVATE_API, this is the packaged-ABI mismatch and the fix isomarchy update, not a reboot. That case has its own record,omarchy-shell-quickshell-undefined-symbol-qt-private-api. - **DPMS wake or monitor hotplug.** Hyprland emits a removal for a transient
FALLBACKoutput Quickshell never recorded as added, desyncing its surface bookkeeping into a fatal Wayland protocol error (issue #7380). On its own this self-heals in about a second, so it only produces a bar that stays gone when it fires six times inside a minute. - **The lockscreen
qFatalafter the quickshell 0.3.1 / Qt 6.11.2 update** (issue #8647). - **Broken user code the shell loads.** A third-party plugin under
~/.config/omarchy/plugins, which runs unsandboxed insideomarchy-shell, or a broken template under~/.config/omarchy/themed.omarchy-theme-set-templatesglobs the user template directory before the shipped one and lets the user copy win, so a badshell.toml.tplthere writes a broken generatedshell.tomlinto the staged theme that the shell then loads. Resettingshell.jsondoes not touch it.
Fix
# 1. Read why it died. The journal is the durable log: Quickshell's own log
# lives on the instance runtime tmpfs and is gone after a reboot.
journalctl --user -b -t omarchy-shell -n 200 --no-pager
# A crash report exists only when Quickshell caught a signal. The Wayland
# fatal-error path leaves through _exit() and writes nothing, and the
# directory itself is absent until the first report, so an empty result here
# is not evidence.
ls -t ~/.cache/quickshell/crashes 2>/dev/null | head
Pick the branch the journal points at.
**undefined symbol: … Qt_6_PRIVATE_API** is the packaged-ABI mismatch, not this problem. Run omarchy update and see the omarchy-shell-quickshell-undefined-symbol-qt-private-api record.
Otherwise:
# 2. Bring it back without logging out. Works from a terminal or over ssh.
# READ THE DANGER FIELD FIRST: on a session that is compositor-locked with
# no live locker, this re-locks the session on purpose.
omarchy-restart-shell # menu: Update > Process > Shell
# 3. Dies again straight away? Take user plugins out of the picture.
mv ~/.config/omarchy/plugins ~/.config/omarchy/plugins.off
omarchy-restart-shell
# 4. Still dying? Take user theme templates out of the picture. These override
# the shipped ones and generate the shell.toml the shell reads.
ls ~/.config/omarchy/themed/*.tpl 2>/dev/null
mv ~/.config/omarchy/themed ~/.config/omarchy/themed.off
omarchy-theme-refresh
omarchy-restart-shell
# 5. Reset the shell config to the shipped default (saves yours as .bak.<epoch>)
omarchy-refresh-config omarchy/shell.json
omarchy-restart-shell
# 6. Hardware whose only visible control went with the bar. These are the
# Update > Hardware menu items, runnable directly:
omarchy-restart-wifi # rfkill unblock wifi; nmcli radio wifi on; rescan
omarchy-restart-bluetooth # rfkill unblock bluetooth
omarchy-restart-audio # restart wireplumber/pipewire/pipewire-pulse, unstick USB cards
omarchy-restart-trackpad
# 7. If quickshell/Qt were upgraded under the running session and step 2 did
# not hold, reboot. The shell cannot be made consistent with a half-swapped
# QML tree.
omarchy-system-reboot
Move plugins.off and themed.off back once you know which one it was.
No graphical session left at all? Switch to a TTY with Ctrl+Alt+F2, log in, and run omarchy-restart-shell there. It derives HYPRLAND_INSTANCE_SIGNATURE from the newest instance runtime dir on its own, and takes OMARCHY_PATH from systemctl --user show-environment, so it works without a login shell.
Verify
omarchy-shell shell ping returns. hyprctl layers | grep omarchy-bar shows the layer. journalctl --user -b -t omarchy-shell stops emitting "relaunching" lines.
Sources
- https://raw.githubusercontent.com/basecamp/omarchy/quattro/bin/omarchy-launch-shell
- https://raw.githubusercontent.com/basecamp/omarchy/quattro/bin/omarchy-restart-shell
- https://raw.githubusercontent.com/basecamp/omarchy/quattro/bin/omarchy-update-restart
- https://raw.githubusercontent.com/basecamp/omarchy/quattro/bin/omarchy-restart-audio
- https://raw.githubusercontent.com/basecamp/omarchy/quattro/bin/omarchy-restart-wifi
- https://raw.githubusercontent.com/basecamp/omarchy/quattro/bin/omarchy-restart-bluetooth
- https://raw.githubusercontent.com/basecamp/omarchy/quattro/default/omarchy/omarchy-menu.jsonc
- https://github.com/basecamp/omarchy/issues/7380
- https://github.com/basecamp/omarchy/issues/8647
- https://raw.githubusercontent.com/omacom/omarchy/quattro/bin/omarchy-launch-shell
- https://raw.githubusercontent.com/omacom/omarchy/quattro/bin/omarchy-restart-shell
- https://raw.githubusercontent.com/omacom/omarchy/quattro/bin/omarchy-theme-set-templates
- https://raw.githubusercontent.com/omacom/omarchy/quattro/bin/omarchy-refresh-config
- https://github.com/omacom/omarchy/issues/7380
- https://github.com/omacom/omarchy/issues/8647
- https://github.com/omacom/omarchy/issues/7106