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

Centre the boot splash and LUKS prompt on a HiDPI panel

omarchyomarchy-4plymouthliminelaptoparch
AUDITED Audited against its sources and confirmed accurate. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Issue #9949 is open and gives the same DPI threshold, the 960x600 arithmetic (x = 80 instead of 560), both outputs affected, and DeviceScale=1 under [Daemon] plus an initramfs rebuild as a verified workaround. The issue used mkinitcpio -P on CachyOS, and the record correctly gives sudo limine-mkinitcpio for Omarchy 4 with -P only on the plain Arch branch. The installed /usr/share/omarchy/default/plymouth/omarchy.script centres from Window.GetWidth() as quoted. Commit 1b001a69 (#11641, 2026-09-13) on quattro adds a layout() that re-centres when the window size changes but still uses Window.GetWidth(), and it is not in 4.0.4-1. The Arch wiki Plymouth HiDPI section documents DeviceScale in /etc/plymouth/plymouthd.conf followed by an initramfs rebuild. pacman -Qii plymouth lists /etc/plymouth/plymouthd.conf as a backup file, so an upgrade leaves a .pacnew. /usr/bin/plymouth-set-default-theme only reads or sets the Daemon Theme key. /usr/lib/initcpio/install/plymouth copies plymouthd.conf into the image, and the plymouth hook is in /etc/mkinitcpio.conf.d/omarchy_hooks.conf. Minor: the sed append is not idempotent, so running it twice adds a duplicate line, which is harmless. Not exercised: the edit, the rebuild or a boot on a HiDPI panel.

RISK

The rebuild replaces /boot/EFI/Linux/omarchy_linux.efi. Let limine-mkinitcpio finish. A typo in plymouthd.conf only affects the splash, but an interrupted rebuild can leave the UKI unbootable, and recovery then means booting a Limine snapshot entry or a live USB.

Symptom

At the LUKS passphrase prompt the Omarchy logo, lock icon, password box and progress bar are bunched into the top-left corner instead of the middle of the screen, with the logo cut off at the left edge. With an external monitor attached, it sits in the top-left quarter there too. Seen on high-DPI laptop and handheld panels (above roughly 192 DPI).

Cause

plymouthd picks a device scale from the panel's DPI. It is a single value for the whole daemon, so every output gets it. At scale 2 the script module reports half the real resolution to the theme (960x600 on a 1920x1200 panel). The 4.0.4 omarchy.script centres with Window.GetWidth() / 2 - logo.image.GetWidth() / 2, so the 800-pixel-wide logo lands at x = 80 instead of 560, and every other element is positioned from the logo. A later upstream commit (#11641, 2026-09-13) re-centres when a display appears late, but still positions from Window.GetWidth(), so it does not address the scale. Issue #9949 is still open.

Fix

Pin Plymouth's scale to 1 and rebuild the image the prompt is drawn from. Add DeviceScale under [Daemon] and keep the existing Theme=omarchy line:


sudo sed -i '/^\[Daemon\]/a DeviceScale=1' /etc/plymouth/plymouthd.conf
cat /etc/plymouth/plymouthd.conf

**Omarchy 4.** The prompt is drawn from inside the UKI, so rebuild it with Omarchy's tool. mkinitcpio -P has no presets to build on Omarchy 4:


sudo limine-mkinitcpio

**Plain Arch.** Regenerate the initramfs with your normal tool, for example sudo mkinitcpio -P where presets exist.

plymouth-set-default-theme, which omarchy-plymouth-set calls, only rewrites the Theme= line, so DeviceScale=1 survives later Style > Unlock changes. /etc/plymouth/plymouthd.conf is a backup file of the plymouth package, so an upgrade leaves a .pacnew instead of overwriting your edit. The trade-off is that the splash is drawn at native pixel size, so the logo is physically smaller on the HiDPI panel.

Verify

grep DeviceScale /etc/plymouth/plymouthd.conf prints DeviceScale=1, and at the next boot the logo and password box sit in the centre of both displays.

Sources

plymouth-splash-off-centre-hidpi