waybar crash after omarchy update (breaks ~/.config/waybar/style.css)

[jason-curtis]

System details

Omarchy 3.3.3

What's wrong?

After running omarchy update to 3.3.3, waybar fails to start and the top bar disappears. The issue is caused by the theme no longer providing a waybar.css file, while the default waybar configuration still tries to import it.

Error

when attempting to run waybar:
[error] style.css:1:46 Failed to import: Error opening file /home/[me]/.config/omarchy/current/theme/waybar.css: No such file or directory

Steps to recreate

1. Use the hackerman theme (it appears this would affect other themes as well)
2. Have waybar configured with the default Omarchy waybar setup that imports ~/.config/omarchy/current/theme/waybar.css
3. Run omarchy update to 3.3.3
4. Waybar crashes on startup because the theme file is missing

Expected behavior

Waybar should continue working after an update, or the update process should handle theme structure changes gracefully.

Workaround

Remove the @import "../omarchy/current/theme/waybar.css"; line in ~/.config/waybar/style.css

Additional context

• The hackerman theme directory contains: colors.toml, btop.theme, neovim.lua, etc., but no waybar.css

[nikolajanke]

I had the same problem.
I don't have much experience using Arch but i did something and it's working.

1. sudo pacman -Syu
2. Super + Alt + Space > Update > Congif > All of them
3. Aether > Blueprints > Use Button
4. Super + Shift + Space

now everything works perfectly

[dhh]

Seems like your upgrade never finished, so the migrations didn't run, so the theme didn't get updated to the new generated model. Make sure omarchy-update finishes fully. If something is blocking, try omarchy-migrate. Then you can run omarchy-theme-set "Tokyo Night" to restore the theme.

[realaaa]

just a quick comment to come back to this, if it happens again, briefly happened, this seems to have helped

hyprctl dispatch exec waybar

[jamescraig17]

Thanks for the update, Aleksey! Good to hear that `hyprctl dispatch exec waybar` helped resolve the crash—though it’s unfortunate this workaround was needed after the Omarchy update broke `~/.config/waybar/style.css`. Since the issue was transient (“briefly happened”), it may have been tied to a race condition or state inconsistency during the update (e.g., Hyprland reinitializing Waybar before config was fully synced or cached). A few suggestions for stability moving forward: 1. **Delay Waybar restart on Hyprland init** In `hyprland.conf`, wrap the Waybar startup in a small delay: ```bash exec-once = sleep 1 && waybar ``` (Adjust delay as needed—1–2s usually sufficient.) 2. **Validate config before restart** Add a pre-flight check in your Waybar launcher script: ```bash #!/bin/sh [ -f "$XDG_CONFIG_HOME/waybar/config.jsonc" ] && waybar || echo "Waybar config missing—skipping" ``` 3. **Watch for Omniarch-specific patches** Since Omarchy modifies Hyprland’s config handling, keep an eye on whether future updates address config reload ordering—or consider reporting this case upstream if reproducible. If the issue reappears consistently, please share: - Omarchy commit hash / version - Waybar version (`waybar --version`) - Relevant logs (`hyprland -d 2>&1 | grep -i waybar`) Thanks again for following up—appreciate the prompt report and workaround! 🙌