OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
omarchy-theming medium occasional DISPUTE

Fix a hand-made theme that silently loses all colors when colors.toml is a relative symlink

omarchythemingdotfiles
AUDITED Audited against its sources and confirmed accurate. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

omarchy-theme-set on 4.0.4-1: line 275 is cp -r "$USER_THEMES_PATH/$THEME_NAME/"* "$NEXT_THEME_PATH/" 2>/dev/null for a theme without .git (theme_came_from_a_repo, line 207). The installed-theme path (stage_installed_theme, line 220) skips symlinks, as the cause says. NEXT_THEME_PATH is ~/.local/state/omarchy/current/next-theme, one level deeper than ~/.config/omarchy/themes/<name>, so a relative link dangles. omarchy-theme-set-templates reads COLORS_FILE from next-theme and generates nothing without it. Issue #9253 (open) reproduces exactly this, and PR #9280 is open and unmerged, so 'not in 4.0.4-1' holds. readlink -f on a relative link resolves from the link's own directory, so the ln -sfn conversion to an absolute target is correct. The second ln line uses the reporter's dotfiles path as an example, which is acceptable as worded.

Symptom

I keep my theme in a dotfiles repo and symlink ~/.config/omarchy/themes/<name>/colors.toml into it. omarchy theme set <name> prints no error, but the bar loses its themed color and opacity and the terminal has no color scheme. Apps that read ~/.local/state/omarchy/current/theme/colors.toml get nothing. stat on that file shows a broken symlink, and current/theme/ghostty.conf is missing.

Cause

For a theme you wrote yourself (no .git directory), omarchy-theme-set stages it with plain cp -r "$USER_THEMES_PATH/$THEME_NAME/"* "$NEXT_THEME_PATH/" (line 275 on 4.0.4-1). cp -r copies a symlink as a symlink. A relative target such as ../../../../dev/dotfiles/.../colors.toml resolves differently once the link sits in ~/.local/state/omarchy/current/theme/, a different directory depth, so it dangles. omarchy-theme-set-templates then has no palette and generates nothing. The script's 2>/dev/null and the missing file checks mean no error appears. Git-installed themes take a different path that refuses symlinks outright.

Fix

Make the link absolute. Its target then resolves the same from any directory:


t=~/.config/omarchy/themes/<name>
readlink "$t/colors.toml"                 # shows the relative target
ln -sfn "$(readlink -f "$t/colors.toml")" "$t/colors.toml"
readlink "$t/colors.toml"                 # now an absolute path
omarchy theme set <name>

If readlink -f prints nothing, the link was already broken in place. Point it at the real file by its full path:


ln -sfn "$HOME/dev/dotfiles/omarchy/.config/omarchy/themes/<name>/colors.toml" "$t/colors.toml"

Do the same for every other symlinked file in the theme directory (backgrounds, preview.png, icons.theme):


find "$t" -maxdepth 2 -type l -lname '[^/]*' -print

That lists every remaining relative link. Upstream PR #9280 dereferences user-theme symlinks while staging, but it is not in 4.0.4-1.

Verify


stat -L ~/.local/state/omarchy/current/theme/colors.toml
ls ~/.local/state/omarchy/current/theme/ghostty.conf

stat -L succeeds and the generated configs exist.

Sources

user-theme-relative-symlink-colors-toml-dangling