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

Make Brave, Chrome or Edge installed with yay/pacman follow the Omarchy theme

omarchychromiumbravechrometheming
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

Confirmed on 4.0.4-1: omarchy-theme-set-browser-policy skips any dir that is missing or a symlink and writes color.json with BrowserThemeColor and BrowserColorScheme. install/helpers/browser-policy.sh lists the four managed dirs, and omarchy-install-browser maps brave, chrome, edge and brave-origin to brave-bin, google-chrome, microsoft-edge-stable-bin and brave-origin-bin and creates the policy dir. omarchy-theme-set-browser refreshes chromium, google-chrome, microsoft-edge-stable, brave and /opt/brave-origin-bin/ only. What the record missed: migration /usr/share/omarchy/migrations/1784510887.sh swaps brave-origin-beta-bin for brave-origin-bin during an update but does not create /etc/brave/policies/managed. Issue #9173 comments confirm that once that dir existed, both Brave Origin and Brave Origin Beta followed the theme, which supports the 'any channel' claim for Brave Origin. Rewrote the fix to cover the migration and dropped the hardcoded brave --refresh-platform-policy, which does nothing for brave-origin and duplicates what omarchy-theme-refresh already does. No directory was created here.

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

Symptom

Chromium follows every Omarchy theme, but the Brave, Google Chrome or Edge I installed myself (yay -S brave-bin, google-chrome, brave-origin-beta-bin) never changes color. It stays light on a dark theme. brave://policy or chrome://policy shows no BrowserThemeColor.

Cause

Theme changes reach Chromium-family browsers only through managed policy. omarchy-theme-set-browser-policy writes color.json into /etc/chromium/policies/managed, /etc/opt/chrome/policies/managed, /etc/opt/edge/policies/managed and /etc/brave/policies/managed. It skips any that does not already exist, and any that is a symlink: [[ -d $policy_dir && ! -L $policy_dir ]] || continue. Only omarchy install browser <name> creates those directories. A browser installed straight from pacman or the AUR has none, so nothing is ever written for it.

Fix

Supported path, for a browser Omarchy offers: install, or reinstall, through Omarchy so it creates the policy directory:


omarchy install browser brave      # or: chrome | edge | brave-origin

This installs a specific package: brave-bin, google-chrome, microsoft-edge-stable-bin or brave-origin-bin. If you run a different channel, such as Chrome Beta, it installs the stable package beside yours, so use the manual path instead.

Brave Origin Beta: on 4.0.4-1 an Omarchy migration (/usr/share/omarchy/migrations/1784510887.sh) replaces brave-origin-beta-bin with brave-origin-bin during omarchy update. It does not create /etc/brave/policies/managed, so a migrated install can still ignore the theme. Use the manual path. The reporter of #9173 found that once that directory existed, both Brave Origin and Brave Origin Beta followed the theme.

Manual path: create the directory with the same ownership and mode Omarchy uses, then re-apply the theme:


# Brave, any channel. For Chrome use /etc/opt/chrome/..., for Edge /etc/opt/edge/...
sudo install -d -m 0755 -o root -g root /etc/brave /etc/brave/policies /etc/brave/policies/managed
omarchy-theme-refresh

omarchy-theme-refresh re-applies the current theme, writes color.json into every policy directory that now exists, and refreshes a running brave, brave-origin (from /opt/brave-origin-bin/), Chromium, Chrome or Edge. Restart any other browser binary to pick up the policy.

Make it a real directory. A symlink such as /etc/brave/policies/managed -> /etc/chromium/policies/managed was the reporter's workaround and does let Brave read Chromium's file. On 4.0.4-1, though, the writer deliberately skips symlinked policy dirs, so a real directory is the form Omarchy maintains.

Verify


cat /etc/brave/policies/managed/color.json

It shows BrowserThemeColor with the current theme's color, and brave://policy lists it.

Sources

aur-chromium-browser-ignores-omarchy-theme-no-policy-dir