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

Fix the Alacritty theme import warning and a theme that silently stops loading

archomarchyalacrittytheming
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

Alacritty's CHANGELOG 0.14.0 moves import, working_directory, live_config_reload and ipc_socket into general, and alacritty/src/migrate/mod.rs moves exactly those keys and prints 'No configuration file found' when it finds no config, which matches the sudo note and the Manjaro thread (user ran sudo alacritty migrate). alacritty-theme#137 quotes the deprecation warning and chrisduerr confirms both TOML forms work. alacritty#8534 shows 'Unused config key: general' on a pre-0.14 build. Arch extra ships alacritty 0.17.0-1. /usr/share/omarchy/config/alacritty/alacritty.toml on 4.0.4-1 starts with the quoted general.import line. One defect: the record tells users on '0.13 or older' to use a top-level TOML import, but the CHANGELOG puts the switch from YAML to TOML in 0.13.0, so 0.12 and earlier ignore alacritty.toml entirely. Cause and fix narrowed to 0.13.x with that caveat.

The cause above was rewritten on 2026-10-05 to match this note; the fix was corrected by the audit itself.

Symptom

Alacritty shows Config warning: import has been deprecated; use general.import instead at startup. Or the opposite: after copying a config from the docs or from Omarchy, the theme does not load and the log says [WARN ] [alacritty_config_derive] Unused config key: general.

Cause

Alacritty 0.14 moved import, together with working_directory, live_config_reload and ipc_socket, into a [general] table. On 0.14 and later a top-level import = [...] still works but warns. On 0.13.x, general.import or a [general] table is an unknown key, ignored with the Unused config key: general warning, so the imported theme never loads. Releases before 0.13 read YAML and ignore alacritty.toml altogether. Omarchy ships general.import = [ "~/.local/state/omarchy/current/theme/alacritty.toml" ] in its Alacritty config, which assumes 0.14 or later. Arch currently packages 0.17.0.

Fix

Check the version first, then use the spelling that version reads:


alacritty --version

Alacritty 0.14 or later (current Arch):


# ~/.config/alacritty/alacritty.toml
[general]
import = ["~/.config/alacritty/themes/tokyo-night.toml"]

general.import = [...] on one line is the same thing. Both forms work. Or let Alacritty rewrite the file:


alacritty migrate

Run alacritty migrate as your user, never with sudo, or it looks for root's config and reports No configuration file found.

Alacritty 0.13.x (another distro's package, or a pinned build): use a top-level import = [...] with no [general] table. Releases before 0.13 do not read TOML at all, so upgrade Alacritty rather than rewriting the file for them.

Omarchy 4: keep the shipped general.import line pointing at ~/.local/state/omarchy/current/theme/alacritty.toml, or theme changes stop reaching Alacritty.

Verify

Start alacritty -vv from another terminal. No deprecated or Unused config key warning appears, and the theme colors are applied.

Sources

alacritty-import-deprecated-general-import