Fix a black screen after the LUKS passphrase is accepted
The recovery approach is sound and the multi-user.target trick is the right instinct. But the cause is half-obsolete and one command is wrong. seamless-login no longer exists on current Omarchy: bin/omarchy-upgrade-to-quattro explicitly removes /etc/systemd/system/omarchy-seamless-login.service and /usr/local/bin/seamless-login and disables the unit. Omarchy 4 boots through SDDM (install/login/sddm.sh). So on a current system the thing to inspect is sddm, not seamless-login. uwsm start hyprland is not the correct invocation, because uwsm takes a desktop entry (hyprland-uwsm.desktop) or an explicit -- separator. Under uwsm the session is also not a hyprland unit, so a journalctl -u hyprland style lookup returns nothing. It is wayland-wm@hyprland.service. Minor: cat file | tail is a useless use of cat, and the quiet/splash removal should go through Omarchy's limine-entry-tool drop-ins rather than hand-editing.
Editing the kernel cmdline at the Limine prompt is temporary and safe, but making it permanent in limine.conf incorrectly can prevent boot. Do not remove the cryptdevice/rd.luks parameters: that makes the encrypted root unreachable.
Symptom
After an update and reboot, the LUKS passphrase prompt appears and accepts the password, then the screen goes black with a blinking cursor. A message flashes for a fraction of a second and is unreadable. Ctrl + Alt + F2 does nothing. The machine is completely inaccessible.
Cause
The graphical session fails to come up after unlock. On Omarchy 4 that means SDDM or the uwsm session, not seamless-login: bin/omarchy-upgrade-to-quattro removes /etc/systemd/system/omarchy-seamless-login.service and /usr/local/bin/seamless-login and disables the unit, and Omarchy 4 boots through SDDM (install/login/sddm.sh). Under uwsm the session is wayland-wm@hyprland.service, not a hyprland unit. Because Omarchy hides the boot text and the session never comes up, there is no TTY handoff either, so the console appears dead. It is a session-startup failure, not a disk-decryption failure.
Fix
Boot into a text-only session so you can read the error. At the Limine menu press e on the Omarchy entry and append to the kernel cmdline:
systemd.unit=multi-user.target
Boot, log in at the console, then read what actually failed. Current Omarchy logs in through SDDM, so check that first:
journalctl -b -1 -p err --no-pager | tail -60
systemctl status sddm
journalctl -b -1 -u sddm --no-pager | tail -40
The compositor runs under uwsm, so look at the session unit rather than a hyprland unit:
journalctl --user -b -1 -u wayland-wm@hyprland.service --no-pager | tail -60
And review the update transcript:
tail -60 /tmp/omarchy-update.log
Try launching the compositor by hand to see the real error text. uwsm wants a desktop entry, not a bare name:
uwsm start hyprland-uwsm.desktop
(If that entry is absent, uwsm start -- Hyprland works as a fallback.)
If it is a driver/session mismatch, the reliable escape is the pre-update snapshot: reboot, pick the dated snapshot entry in the Limine menu, then run omarchy-snapshot restore.
To make future failures debuggable, drop the silent-boot flags. On Omarchy these live in limine-entry-tool drop-ins, so edit there and regenerate rather than hand-editing the bootloader config:
ls /etc/limine-entry-tool.d/
sudo limine-mkinitcpio
Verify
systemctl --user status shows the graphical session units active after a normal boot, and the desktop appears without the black-screen stall.