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

Fix the transparent bar keeping the previous theme's text color after a theme switch

omarchybarquickshelltheming
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Bar.qml on 4.0.4-1: line 1061 is if (!requestedTransparent || transparentForegroundProc.running) return, and the Process has no onExited re-arm, so the cause is right and matches issue #10289 (open, with the /proc trace showing only the old palette sampled). omarchy bar transparent <true|false> exists in omarchy-bar and writes .bar.transparent to ~/.config/omarchy/shell.json via jq -S, and setRequestedTransparency(false then true) schedules a fresh sample, so the manual workaround is sound. The hook needs two fixes. omarchy-theme-set calls omarchy-hook theme-set synchronously (line 341) before the theme-switcher preload, so the hook's 3 s of sleep delays every theme switch. It should run in the background. And the grep '"transparent": *true' guard matches any transparent key in shell.json, not only the bar's, so it is replaced with jq -e '.bar.transparent == true', which reads the exact key omarchy-bar writes.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.

Symptom

I run the bar transparent (omarchy bar transparent true). After switching themes, everything changes except the bar's text and icons, which keep the old theme's color. Going from a light theme to a dark one leaves dark text on a dark wallpaper, nearly unreadable. Double-clicking the bar twice (transparency off, then on) fixes it immediately.

Cause

In a transparent bar, the shell samples the wallpaper with omarchy-bar-text-color (ImageMagick, about 0.5 s on a large wallpaper) to choose a readable foreground. refreshTransparentForeground() in /usr/share/omarchy/shell/plugins/bar/Bar.qml returns early when a sample is already running (line 1061 on 4.0.4-1), and nothing re-arms the request. A theme switch fires once when current/theme is swapped, still with the old palette. It fires again when the new palette arrives over IPC, which lands while the first sample is running and is dropped. The bar keeps the color computed for the old palette.

Fix

After a theme switch, force a fresh sample by turning transparency off and on:


omarchy bar transparent false && sleep 1 && omarchy bar transparent true

Or double-click an empty part of the bar twice, which the reporter verified. Turning transparency off resets the text to the theme foreground, and turning it on schedules a new sample after the palette and wallpaper have settled.

To do it on every switch, add a theme-set hook. omarchy theme set waits for its hooks, so the hook puts its work in the background rather than holding up the switch:


mkdir -p ~/.config/omarchy/hooks/theme-set.d
cat > ~/.config/omarchy/hooks/theme-set.d/50-bar-resample.sh <<'EOF'
#!/bin/bash
jq -e '.bar.transparent == true' ~/.config/omarchy/shell.json >/dev/null 2>&1 || exit 0
(
  sleep 2
  omarchy bar transparent false
  sleep 1
  omarchy bar transparent true
) >/dev/null 2>&1 &
EOF
chmod +x ~/.config/omarchy/hooks/theme-set.d/50-bar-resample.sh

The jq test reads .bar.transparent, the key omarchy bar transparent writes. The real fix, a pending flag re-run from onExited, is proposed in the issue and is not in 4.0.4-1.

Verify

Switch from rose-pine to tokyo-night with transparency on, run the command, and the bar text turns light within a second or two.

Sources

transparent-bar-text-keeps-previous-theme-color