Fix Style > Unlock failing with "refusing to publish" on a machine upgraded from Omarchy 3
Read /usr/share/omarchy/bin/omarchy-plymouth-set on 4.0.4-1. It refuses EUID 0 with the quoted 'run omarchy-plymouth-set as your user, not under sudo.' message. It runs its privileged half via sudo /bin/bash -c. Its validate_trusted_directory walks each level up to / requiring uid 0 and no 0022 bits, and prints the exact refusal quoted in the symptom. It validates /usr/share/plymouth/themes/omarchy, its logos subdirectory and /usr/share/sddm/themes/omarchy. It ends with sudo limine-mkinitcpio, as the danger says. omarchy-plymouth-reset calls refresh-plymouth and refresh-sddm through the same validator, and omarchy-plymouth-current prints 'default' when logo.png matches the packaged one. The Style > Unlock entry in default/omarchy/omarchy-menu.jsonc calls omarchy-plymouth-set-by-theme. Both cited issues (#11640 and #11396, both open, on 4.0.3-1) report the user-owned 0700 directory on pre-4.0 installs, the omarchy-settings mtree mismatch, pacman not re-chowning existing directories, and the chown root:root plus chmod 755 repair. #11396 also names 695614ce's earlier cp -a publishing. None of the 4.0.4-1 migrations or the 37 newer quattro migrations touch these directories (grepped). On this workstation all three directories are already root:root 755, so the failure itself was not reproduced, and no chown or set was run.
A successful set rebuilds the UKI with sudo limine-mkinitcpio. Let it finish. Interrupting it can leave /boot/EFI/Linux/omarchy_linux.efi incomplete. Change ownership only on the directories listed: a recursive chown on the wrong path under /usr can break packages.
Symptom
Picking a theme in Style > Unlock, or running omarchy-plymouth-set-by-theme tokyo-night, asks for the sudo password and then stops with omarchy-plymouth-set: refusing to publish: directory /usr/share/plymouth/themes/omarchy (must be root-owned and not group- or world-writable) failed validation. The boot splash and the LUKS passphrase prompt keep the default design, omarchy plymouth current keeps printing default, and omarchy plymouth reset fails with the same message. Seen on installs that started on Omarchy 3 and were upgraded to 4.
Cause
Older Omarchy installers published the Plymouth theme with cp -a from a user-owned staging directory, which left /usr/share/plymouth/themes/omarchy owned by the desktop user with mode 0700. Since Omarchy 4.0.0 that path belongs to the omarchy-settings package, whose metadata expects root:root and 0755, but pacman does not re-chown a directory that already exists, so the old metadata survives every upgrade. pacman -Qkk omarchy-settings reports it as a UID, GID and permission mismatch.
The 4.0.x omarchy-plymouth-set runs its privileged half through sudo /bin/bash -c and, before publishing any asset, walks each destination directory up to / and requires every level to be owned by uid 0 with no group or world write bit. A user-owned theme directory fails that check, so every set, every reset and every switcher selection is refused before anything is written. The same check is applied to /usr/share/sddm/themes/omarchy. As of 4.0.4 no migration repairs the directory: the migrations in the package and the newer ones on the upstream quattro branch (checked 2026-10-04) do not touch it, and the refusal message does not say how to fix it.
Fix
Check the three directories the publisher validates:
stat -c '%U:%G %a %n' /usr/share/plymouth/themes/omarchy /usr/share/plymouth/themes/omarchy/logos /usr/share/sddm/themes/omarchy
pacman -Qkk omarchy-settings 2>&1 | grep -E 'plymouth|sddm'
Any of them that is not root:root 755 is the blocker. Restore the packaged ownership and mode on exactly those directories. Do not run a recursive chown over /usr/share:
for d in /usr/share/plymouth/themes/omarchy /usr/share/plymouth/themes/omarchy/logos /usr/share/sddm/themes/omarchy; do
[[ -d $d ]] || continue
sudo chown root:root "$d"
sudo chmod 755 "$d"
done
Then apply the theme again as your normal user. Do not use sudo, because omarchy-plymouth-set refuses to run as root (Error: run omarchy-plymouth-set as your user, not under sudo.) and asks for the password itself:
omarchy-plymouth-set-by-theme tokyo-night
omarchy plymouth current
Or pick it again in Super+Space > Style > Unlock.
Verify
stat -c '%U:%G %a' /usr/share/plymouth/themes/omarchy prints root:root 755, pacman -Qkk omarchy-settings no longer lists the Plymouth or SDDM directories, omarchy plymouth current prints the theme you chose, and the next boot shows that theme's logo and colours at the passphrase prompt.