Stop the Plymouth/SDDM unlock screen reverting to default after every update
Checked every claim against the shipped scripts on this workstation (omarchy 4.0.2-1, omarchy-settings 4.0.2-1, sddm 0.21.0-7, plymouth 26.134.222-2) rather than against the issue text. Confirmed locally: omarchy-plymouth-set publishes into /usr/share/plymouth/themes/omarchy and /usr/share/sddm/themes/omarchy, pacman -Qo names omarchy-settings 4.0.2-1 as the owner of both logo.png and Main.qml, and pacman -Qii omarchy-settings lists six backup files, none of them under those two directories, so pacman overwrites them silently on upgrade. Confirmed omarchy-update runs omarchy-update-system-pkgs (which is sudo pacman -Syu --noconfirm --overwrite '/usr/share/omarchy/*'), then omarchy-migrate, then omarchy-hook post-update, in that order, so a post-update hook is the right place and runs after the package that reverts the theme. Confirmed nothing re-applies it: the only two migrations mentioning plymouth are 1784917531.sh (adds initramfs_async=0) and 1788025225.sh (removes a retired omarchy-plymouth-shutdown.service), and neither restores a theme. Confirmed omarchy-plymouth-current holds no state and derives the answer by byte-comparing logo.png, which is why it reports default after a revert.
Confirmed the record is describing the right system, which the brief flagged as the risk. It does not name hyprlock, and the Omarchy 4 session lock is a separate thing: an ext-session-lock surface drawn by omarchy-shell. SDDM is genuinely installed, enabled and active here (/etc/systemd/system/display-manager.service points at /usr/lib/systemd/system/sddm.service), and /usr/share/sddm/themes/omarchy exists, so naming SDDM is correct rather than borrowed from another distro. The "Style > Unlock" path is real: style.unlock in /usr/share/omarchy/default/omarchy/omarchy-menu.jsonc runs omarchy-plymouth-switcher and then omarchy-plymouth-set-by-theme. vantablack is one of the 23 names omarchy-plymouth-list returns here.
Two defects in the fix. It re-applies unconditionally on every omarchy update, and omarchy-plymouth-set ends with sudo limine-mkinitcpio, so as written it adds a full initramfs and UKI rebuild to every update including ones where omarchy-settings was never upgraded. The corrected hook guards on omarchy plymouth current. It also never says the hook needs sudo: omarchy-plymouth-set carries omarchy:requires-sudo=true, refuses to run when EUID is 0, and calls sudo itself, so it can prompt for a password in the middle of an update and will do so under omarchy update -y. The danger field understated the consequence: on Omarchy 4 an interrupted rebuild is limine-mkinitcpio regenerating the UKI at /boot/EFI/Linux/omarchy_linux.efi, which risks an unbootable machine rather than an unreadable splash. Read issue 6864 in full: it is OPEN, created 2026-08-14 against 4.0.0rc5-1, and it supports every claim the record's cause makes.
Two smaller points left alone because the verdict schema has no field for them. applies_to carries systemd-boot and grub, and Omarchy 4 boots a UKI through Limine, so those two tags do not apply on Omarchy 4. The symptom says the revert follows "the next omarchy update" when it in fact follows the next update that upgrades omarchy-settings, which the verify field already states correctly, so verify carries the precise version. Severity low and frequency common both stand: the loss is cosmetic and recoverable, and it recurs on every omarchy-settings upgrade for anyone who set a custom unlock screen.
Not exercised: I did not run omarchy update, did not run omarchy plymouth set-by-theme, did not rebuild any initramfs, and did not install the hook. Everything above was read from the shipped scripts, pacman -Q output and the upstream issue. Whether the guarded hook completes without a password prompt inside a real update depends on the sudo timestamp surviving the pacman step, and that was not measured.
omarchy plymouth set-by-theme rewrites files inside the Plymouth theme directory and then rebuilds the initramfs. On Omarchy 4 that is sudo limine-mkinitcpio, which regenerates the UKI at /boot/EFI/Linux/omarchy_linux.efi, so an interrupted rebuild risks a machine that does not boot, not just an ugly splash. On a LUKS-encrypted machine the same rebuild is what carries the Plymouth password prompt, so keep a bootable USB around before experimenting. Do not run this concurrently with omarchy update, which is already holding omarchy-update-lock and may be rebuilding the initramfs itself, and do not add an unguarded re-apply to post-update.d, because that puts an initramfs rebuild into every update whether or not anything reverted.
Symptom
You pick a custom unlock screen via Style > Unlock and it applies. After the next omarchy update, the boot splash (including the LUKS password prompt) and the SDDM logout screen are back to the default green/yellow Omarchy design. omarchy plymouth current now reports default.
Cause
omarchy-plymouth-set writes the recolored assets straight into package-owned directories, /usr/share/plymouth/themes/omarchy/ and /usr/share/sddm/themes/omarchy/, both owned by the omarchy-settings package. omarchy update runs omarchy-update-system-pkgs, which is sudo pacman -Syu --noconfirm --overwrite '/usr/share/omarchy/*', and that upgrades omarchy-settings and restores those files to the shipped defaults. Neither directory is in the package's backup array, so pacman overwrites without leaving a .pacnew.
Unlike omarchy theme set, the plymouth setter persists no state anywhere. omarchy-plymouth-current works it out after the fact by byte-comparing the installed /usr/share/plymouth/themes/omarchy/logo.png against each theme's unlock.png, which is exactly why the reverted state reads back as default. Nothing re-applies the selection: omarchy-update calls omarchy-update-system-pkgs, then omarchy-migrate, then omarchy-hook post-update, and none of the shipped migrations or hooks restore a plymouth or sddm theme.
This is Omarchy 4's boot splash and SDDM greeter, not the session lock screen. The session lock on Omarchy 4 is an ext-session-lock surface drawn by omarchy-shell (Quickshell) and is styled by ~/.config/omarchy/shell.toml, and hyprlock is not installed. SDDM is installed, enabled and active on Omarchy 4, so the SDDM half of this is real and not a leftover from another distro.
Fix
Record your choice and re-apply it after an update that reverted it. Save the selection:
mkdir -p ~/.local/state/omarchy
echo vantablack > ~/.local/state/omarchy/unlock.name
Add a post-update hook. omarchy-hook runs every non-.sample file in the directory with bash, so the name and the executable bit do not matter, but the guard does: omarchy plymouth set-by-theme rebuilds the initramfs, so re-applying blindly adds a limine-mkinitcpio run to every single update:
mkdir -p ~/.config/omarchy/hooks/post-update.d
cat > ~/.config/omarchy/hooks/post-update.d/50-replymouth.sh <<'EOF'
#!/bin/bash
name_file=~/.local/state/omarchy/unlock.name
[[ -f $name_file ]] || exit 0
want=$(cat "$name_file")
[[ -n $want ]] || exit 0
# Only re-apply when the package upgrade actually reverted it.
[[ "$(omarchy plymouth current)" == "$want" ]] && exit 0
omarchy plymouth set-by-theme "$want"
EOF
omarchy plymouth set-by-theme calls omarchy-plymouth-set, which is marked requires-sudo and runs sudo plymouth-set-default-theme omarchy plus sudo limine-mkinitcpio itself. It refuses to run under sudo, so leave the hook unprivileged. It can prompt for a password inside the update. If you run omarchy update -y unattended, expect that prompt, or re-apply by hand instead.
Manual re-apply any time:
omarchy plymouth set-by-theme vantablack
omarchy plymouth current
List what you can pick from, and reset to stock:
omarchy plymouth list
omarchy plymouth reset
Confirm what pacman owns, to see why it keeps reverting:
pacman -Qo /usr/share/plymouth/themes/omarchy/logo.png
pacman -Qo /usr/share/sddm/themes/omarchy/Main.qml
grep 'omarchy-settings' /var/log/pacman.log | tail -3
The hook itself survives updates: ~/.config/omarchy/hooks/post-update.d/ is user-owned and no package replaces it. The plymouth theme does not, which is the whole point of the hook. Upstream issue #8357's always_copy_config_files list does not cover hooks/post-update.d, so only a re-run of omarchy-upgrade-to-quattro would go near it. This is a workaround for an open upstream bug, not a setting, so drop the hook once upstream persists the selection itself.
Verify
omarchy plymouth current reports your theme immediately after an omarchy update that upgraded omarchy-settings, and pacman -Qo /usr/share/plymouth/themes/omarchy/logo.png still names omarchy-settings while the file's mtime is later than the upgrade line in /var/log/pacman.log. At the next boot the LUKS prompt shows the custom splash.