Make the boot splash and LUKS prompt follow a theme change
Read /usr/share/omarchy/bin/omarchy-theme-set, omarchy-plymouth-set-by-theme, omarchy-plymouth-list, omarchy-plymouth-set, omarchy-plymouth-current, omarchy-theme-dir, omarchy-theme-color and omarchy-launch-floating-terminal-with-presentation on 4.0.4-1, and diffed each against the quattro tree on 2026-10-05. post_theme_commands has no Plymouth step on 4.0.4 or on quattro (quattro only adds omarchy-theme-set-hunk). The style.unlock entry in default/omarchy/omarchy-menu.jsonc runs omarchy-plymouth-set-by-theme in omarchy-launch-floating-terminal-with-presentation exactly as the hook does. omarchy-plymouth-list filters on preview-unlock.png, omarchy-plymouth-set rejects a missing or symlinked logo and prints both quoted error strings verbatim, refuses EUID 0, and runs sudo limine-mkinitcpio when present. omarchy-plymouth-set-by-theme reads only the literal background and foreground keys by awk (its fallback argument is never passed), and omarchy-theme-color does resolve bg/fg/color0/color7, so the --file repair line is correct. All 22 stock themes ship unlock.png, preview-unlock.png and both keys (counted on this machine). omarchy plymouth current was run read-only and prints default. The record unlock-screen-theme-reverts-after-omarchy-update exists in the corpus. Not exercised: an actual apply or a reboot, because both need sudo and rebuild the UKI.
Every apply rebuilds the UKI with sudo limine-mkinitcpio, which takes time and asks for the sudo password. With the optional hook that happens on every theme change whose splash differs. Do not close the terminal while the rebuild runs. Never run it under sudo, because the setter refuses that.
Symptom
omarchy theme set catppuccin, or a pick in the theme picker, retints the desktop, but the boot splash, the LUKS passphrase prompt and the SDDM screen keep the previous theme or the stock Omarchy design. A theme I made myself is not in Super+Space > Style > Unlock at all. Applying it by hand fails with Logo file not found: /home/<user>/.config/omarchy/themes/<name>/unlock.png or Invalid background color: (expected #RRGGBB).
Cause
The boot screen is not part of a theme change. omarchy-theme-set runs a fixed post_theme_commands list (terminal, hyprctl, btop, foot, tmux, gnome, browser, vscode and others) and no Plymouth step is in it. The splash is set separately: the Style > Unlock menu entry runs omarchy-plymouth-set-by-theme <name> in a floating terminal, because it needs sudo and rebuilds the UKI with limine-mkinitcpio.
Three requirements decide whether a custom theme can be used. omarchy-plymouth-list, which feeds the Unlock picker, lists only themes that contain preview-unlock.png. omarchy-plymouth-set-by-theme uses the theme's unlock.png as the logo, and omarchy-plymouth-set refuses a logo that is missing or is a symlink. It also reads the colours with a plain awk match on the literal keys background and foreground in colors.toml. A theme that only defines legacy names (bg, fg, color0), which omarchy-theme-color would resolve, hands an empty string to the setter, which rejects it. All 22 stock themes in 4.0.4 ship both images and both keys.
Fix
Apply the current theme to the boot screen once, from a terminal, as your user:
theme=$(cat ~/.local/state/omarchy/current/theme.name)
omarchy-plymouth-set-by-theme "$theme"
omarchy plymouth current
For a custom theme, check the three requirements:
d=~/.config/omarchy/themes/<name>
ls -l "$d/unlock.png" "$d/preview-unlock.png" # both must exist as regular files, not symlinks
grep -E '^(background|foreground) *=' "$d/colors.toml"
If preview-unlock.png is missing, the picker has no thumbnail and leaves the theme out. Reusing the logo is enough:
cp "$d/unlock.png" "$d/preview-unlock.png"
If the colour keys are missing, write them out from what Omarchy resolves:
printf 'background = "%s"\nforeground = "%s"\n' \
"$(omarchy-theme-color --file "$d/colors.toml" background)" \
"$(omarchy-theme-color --file "$d/colors.toml" foreground)" >> "$d/colors.toml"
Optional, to follow every theme change automatically. A theme-set hook cannot answer a sudo prompt when the change comes from the picker, so this hook opens the same floating terminal the Unlock menu uses, and does nothing when the splash already matches:
mkdir -p ~/.config/omarchy/hooks/theme-set.d
cat > ~/.config/omarchy/hooks/theme-set.d/50-plymouth.sh <<'EOF'
#!/bin/bash
theme="$1"
[[ -f $(omarchy-theme-dir "$theme")/unlock.png ]] || exit 0
[[ $(omarchy-plymouth-current) == "$theme" ]] && exit 0
omarchy-launch-floating-terminal-with-presentation "omarchy-plymouth-set-by-theme $(printf %q "$theme")"
EOF
An omarchy update that upgrades omarchy-settings still puts the stock splash back. That is a separate problem with its own record, unlock-screen-theme-reverts-after-omarchy-update.
Verify
omarchy plymouth current prints the active theme name, the theme appears as a tile in Style > Unlock, and the next boot shows its logo and background colour at the passphrase prompt.
Sources
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-theme-set
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-plymouth-set-by-theme
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-plymouth-list
- https://github.com/omacom/omarchy/blob/quattro/bin/omarchy-plymouth-set
- https://github.com/omacom/omarchy/blob/quattro/default/omarchy/omarchy-menu.jsonc