Bring Waybar back after an Omarchy 3 update when style.css cannot import waybar.css
#4327 supports the symptom and dhh's comment supports the cause (upgrade did not finish, migrations did not run, theme not moved to the generated model. Run omarchy-migrate then omarchy-theme-set). Checked the 3.x tree at tags: v3.2.3 themes ship waybar.css, v3.3.0 and v3.3.3 ship default/themed/waybar.css.tpl and no per-theme waybar.css, config/waybar/style.css line 1 is the quoted @import, and bin/omarchy-migrate, omarchy-theme-set and omarchy-restart-waybar exist. Defect in the fix: it reads the theme name from ~/.config/omarchy/current/theme.name, but v3.2.3's omarchy-theme-set wrote no such file (it symlinked current/theme), so on exactly the interrupted 3.2 to 3.3 upgrade this record is about the file can be missing, cat yields nothing and omarchy-theme-set exits with its usage message. Also v3.3.3's omarchy-theme-set-templates generates templates only when the theme has colors.toml, so an old third-party theme still ends with no waybar.css. Fix rewritten for both. Omarchy 4 line confirmed: no waybar package on 4.0.4-1 and the 3 to 4 upgrade removes it.
Symptom
Omarchy 3.x: after omarchy update the top bar is gone. Running waybar in a terminal prints:
[error] style.css:1:46 Failed to import: Error opening file /home/<user>/.config/omarchy/current/theme/waybar.css: No such file or directory
Cause
From Omarchy 3.3 the theme directory no longer ships a static waybar.css. It is generated from default/themed/waybar.css.tpl into ~/.config/omarchy/current/theme/ when a theme is applied. ~/.config/waybar/style.css still starts with @import "../omarchy/current/theme/waybar.css";. If the update did not finish, its migrations never ran, the theme was never re-staged into the generated model, and the import target does not exist. Waybar treats a failed import as fatal.
Fix
Omarchy 3.x: finish the migrations first:
omarchy-migrate
If a migration fails, omarchy-migrate asks whether to skip it. Read the error before you answer.
Then re-apply the theme so the file is generated. 3.3 and later record the theme name in ~/.config/omarchy/current/theme.name. Releases before 3.3 kept a symlink at ~/.config/omarchy/current/theme and wrote no such file, so after an interrupted upgrade from 3.2 it may be missing:
theme=$(cat ~/.config/omarchy/current/theme.name 2>/dev/null || basename "$(readlink ~/.config/omarchy/current/theme)")
echo "$theme"
omarchy-theme-set "$theme"
ls ~/.config/omarchy/current/theme/waybar.css
omarchy-restart-waybar
If echo prints nothing, name the theme yourself, as the maintainer suggested in #4327:
omarchy-theme-set "Tokyo Night"
omarchy-theme-set generates waybar.css only for a theme that has a colors.toml. A third-party theme written before 3.3 that ships neither colors.toml nor its own waybar.css leaves the import broken, so switch to a stock theme or an updated version of that theme.
Stopgap only: removing the first line of ~/.config/waybar/style.css (@import "../omarchy/current/theme/waybar.css";) lets Waybar start, but the bar then has no theme colors. Restore the line once the theme is fixed.
Omarchy 4: there is no Waybar. The bar is part of omarchy-shell, so this does not apply.
Verify
pgrep -x waybar
It returns a PID, and waybar run by hand prints no import error.