Zed install ends with '[WARN] Could not determine current Omarchy theme' from omazed
I read issue omacom/omarchy#7325 in full with comments. It supports the mechanism but not the channel. marijn070's comment gives exactly the path pair the record cites, and Thijzert123 confirmed the fix, so the cause is well sourced. I verified the mechanism against the omazed source itself: at tag v2.0.1 omazed line 5 is OMARCHY_THEME_PATH="$HOME/.config/omarchy/current/theme" and line 319 emits Could not determine current Omarchy theme, and all four lines the symptom quotes appear in that file at lines 126, 111, 122 and 319. At tag v2.1.0 lines 5 to 7 add OMARCHY_THEME_PATH_V4="$HOME/.local/state/omarchy/current/theme" and a detect_omarchy_version function that reads omarchy-version and otherwise tests for the Omarchy 4 state directory. Commit 302cd396 is dated 2026-08-15 and gh api repos/aps6/omazed/compare/302cd396...v2.1.0 reports behind_by 0, so it is in v2.1.0 as the record says. Confirmed on this Omarchy 4.0.2-1 workstation: ~/.local/state/omarchy/current/theme/colors.toml and ~/.local/state/omarchy/current/theme.name exist, theme.name reads gruvbox, and ls ~/.config/omarchy/current returns No such file or directory. The keybinding in the verify block is right, /usr/share/omarchy/default/hypr/bindings/utilities.lua line 18 binds SUPER + SHIFT + CTRL + SPACE to the theme menu. What is wrong is the fix and the last sentence of the cause. The Omarchy menu does not install omazed from the AUR. On this machine /usr/share/omarchy/bin/omarchy-install-editor-zed runs omarchy-pkg-add zed omazed, and /usr/share/omarchy/bin/omarchy-pkg-add is plain sudo pacman -S --noconfirm --needed, which can only resolve from a repository. omazed is in the [omarchy] repository: pacman -Si omarchy/omazed here reports 2.1.0-2 and the stable omarchy.db I fetched on 2026-09-11 carries omazed-2.1.2-1. Its PKGBUILD history in omacom/omarchy-pkgs shows 2.0.1-1 from 2026-05-29 and 2.1.0-2 from 2026-08-15T18:34Z, which is the real reason the reporter hit it on 2026-08-17 on a fresh 4.0.0 install: the offline ISO leaves the [omarchy] database unsynced, so pacman -S omazed installed the old 2.0.1-1. So yay -S aur/omazed is the wrong layer. It happens to work, because the AUR PKGBUILD builds the same v$pkgver release tarball, but it replaces a repository-tracked package with a local build for no reason. I rewrote the fix around omarchy update, which I confirmed runs pacman -Syu in /usr/share/omarchy/bin/omarchy-update-system-pkgs and yay -Sua in omarchy-update-aur-pkgs, so it covers both channels. I could not exercise the bug: neither zed nor omazed is installed here (pacman -Q omazed errors), I have no sudo, and I did not run omazed setup or switch themes. The version floor and the 2.0.x to 2.1.0 diff come from the upstream git tags, not from a local install.
Symptom
Installing Zed from the Omarchy menu (Install > Editor > Zed, which runs omarchy-install-editor-zed) installs the zed and omazed packages, then omazed setup prints:
[INFO] Setting up Omazed for user: user
[INFO] Removed old omazed hook
[SUCCESS] ✓ Omarchy hook configured
[WARN] Could not determine current Omarchy theme
Zed opens with its default theme and does not follow the Omarchy theme. Running omazed setup again gives the same warning. Reported on a fresh Omarchy Quattro (4.0.0) install.
Cause
Named by the person who fixed it in the thread and confirmed against the omazed source. omazed 2.0.x read the active theme from ~/.config/omarchy/current/theme, which is where Omarchy 3 kept it. At tag v2.0.1 the script sets that path on line 5 and warns Could not determine current Omarchy theme on line 319 when nothing is found there. Omarchy 4 keeps state under ~/.local/state/omarchy/, so the current theme is ~/.local/state/omarchy/current/theme and ~/.config/omarchy/current does not exist at all. omazed commit 302cd396 (2026-08-15), one commit behind the v2.1.0 tag, added a detect_omarchy_version probe that reads omarchy-version and otherwise tests for the Omarchy 4 state directory, then selects the matching theme path with the Omarchy 3 path kept as a fallback.
The channel is what decides the fix, and it is pacman rather than the AUR. omarchy-install-editor-zed runs omarchy-pkg-add zed omazed, and omarchy-pkg-add is plain sudo pacman -S --needed, so omazed comes from the [omarchy] repository. That repository carried omazed 2.0.1-1 from 2026-05-29 and only moved to 2.1.0-2 on 2026-08-15. A fresh Omarchy 4.0.0 machine installs from the offline ISO and has no synced [omarchy] database, so pacman -S omazed installs whatever the stale database names, which is the 2.0.1-1 build with the Omarchy 3 path. The AUR also carries omazed, built from the same v$pkgver release tarball, so an AUR installation older than 2.1.0 has the same defect.
Fix
Update omazed, then run its setup again. omazed comes from the [omarchy] pacman repository, so the supported path is an ordinary Omarchy update, which syncs that repository's database and pulls the fixed build:
omarchy update
pacman -Q omazed # 2.1.0 or newer
omazed setup
The [omarchy] repository shipped the fix as 2.1.0-2 and serves 2.1.2-1 as of 2026-09-11, so any current update clears the floor.
Do not run pacman -Syu directly, because Omarchy's ALPM guard blocks it, and never pacman -Sy omazed, which is a partial upgrade. If you want just this package now rather than a full Omarchy update, sync and upgrade in one transaction:
OMARCHY_ALLOW_DIRECT_PACMAN=1 sudo pacman -Syu omazed
omazed setup
If you installed omazed from the AUR rather than through the Zed menu entry, omarchy update still covers it, because it runs yay -Sua for foreign packages after the pacman pass. To rebuild that one package on its own:
yay -S --noconfirm aur/omazed
omazed setup
Plain Arch users of omazed are not affected unless they also run Omarchy 4.
Verify
omazed setup # ends without the [WARN] line
ls ~/.local/state/omarchy/current/theme/colors.toml
Change the Omarchy theme (Super+Ctrl+Shift+Space) and Zed's theme changes with it.
Sources
- https://github.com/omacom/omarchy/issues/7325
- https://github.com/aps6/omazed/commit/302cd396
- https://aur.archlinux.org/packages/omazed
- https://github.com/aps6/omazed/commit/302cd396be88cf508a05d97edcdc7d48eafdc299
- https://github.com/aps6/omazed/blob/v2.0.1/omazed
- https://github.com/aps6/omazed/blob/v2.1.0/omazed
- https://github.com/omacom/omarchy-pkgs/blob/master/pkgbuilds/omazed/PKGBUILD
- https://github.com/omacom/omarchy-pkgs/commits/master/pkgbuilds/omazed/PKGBUILD
- https://pkgs.omarchy.org/stable/x86_64/omarchy.db