Recover a black screen at boot after selecting a stock SDDM theme (maya, maldives, elarun)
Mechanism confirmed on this 4.0.4-1 workstation and in #10302 (maintainer reproduction on a 4.0.2 VM): /usr/bin/sddm-greeter and sddm-greeter-qt6 both exist, only /usr/share/sddm/themes/omarchy/metadata.desktop has QtVersion=6, elarun/maldives/maya lack it, qt5-base and qt5-declarative are not installed, and sddm 0.21.0-7 lists qt5-declarative as an optdep 'for using Qt5 themes'. /etc/sddm.conf.d holds 10-theme.conf and 10-wayland.conf (omarchy-settings) plus unowned 99-omarchy-login.conf and autologin.conf, as the record says. Two defects in the fix. First, the sed only touches /etc/sddm.conf.d/*.conf, while the record itself (and #10302) says a .pacnew, editor backup or /etc/sddm.conf can carry the winning Current= line, so the repair could leave the fatal value in place. Second, the closing claim that the Arch wiki says themes given QtVersion=6 'may then fail with Library import requires a version' misreads the wiki: the wiki gives that error as the symptom of a Qt6 theme that LACKS QtVersion=6 and tells you to add the key. The advice not to edit package-owned metadata.desktop stands, with the correct reason. Cause, symptom, verify and danger hold. Nothing was exercised: no theme was changed and sddm was not restarted.
Removing autologin while a Qt5-only theme is configured is what turns this from latent into an unbootable graphical login. Check grep -Hn '^Current=' /etc/sddm.conf.d/* before deleting autologin.conf.
Symptom
After setting the SDDM login theme to maya, maldives or elarun, or a third-party theme, the machine boots to a permanent black screen with no login. It often shows up only after removing autologin, which had been skipping the greeter. journalctl -b -1 -u sddm shows:
sddm-helper-start-wayland: "/usr/bin/sddm-greeter: error while loading shared libraries: libQt5Quick.so.5: cannot open shared object file: No such file or directory"
sddm-helper-start-wayland: wayland greeter finished 127 QProcess::NormalExit
sddm-helper-start-wayland: "(EE) could not connect to wayland server"
Cause
SDDM picks its greeter from the theme's metadata.desktop. QtVersion=6 selects /usr/bin/sddm-greeter-qt6, and a theme without it gets the Qt5 binary /usr/bin/sddm-greeter. Omarchy 4 dropped the Qt5 stack (commit fae4a9e0, first in v4.0.0-beta3), so a fresh 4.x install has no Qt5 packages. Only the omarchy theme declares QtVersion=6. The three themes shipped by the sddm package do not, and SDDM never falls back when the Qt5 greeter exists but cannot load its libraries. An empty or nonexistent theme name is safe, because SDDM uses its embedded Qt6 theme. Only a real Qt5-only theme is fatal. Autologin (/etc/sddm.conf.d/autologin.conf) skips the greeter entirely, which hides the setting until autologin is removed.
Fix
Switch to a text console with Ctrl+Alt+F2 and log in. If no console comes up, boot the Omarchy ISO and edit the same files on the mounted root.
Find which file sets the theme. SDDM reads /usr/lib/sddm/sddm.conf.d/, then /etc/sddm.conf.d/ in sorted order, then /etc/sddm.conf, and the last Current= wins. Any file in that directory counts, including .pacnew and editor backups:
grep -Hn '^Current=' /usr/lib/sddm/sddm.conf.d/* /etc/sddm.conf.d/* /etc/sddm.conf 2>/dev/null
grep -L '^QtVersion=6' /usr/share/sddm/themes/*/metadata.desktop # the themes that will brick
Omarchy 4: set every Current= line under /etc back to omarchy, in every file the first grep listed and not only the *.conf ones. On a 4.x ISO install the usual files are 10-theme.conf (owned by omarchy-settings) and 99-omarchy-login.conf:
for f in /etc/sddm.conf.d/* /etc/sddm.conf; do
[[ -f $f ]] && grep -q '^Current=' "$f" && sudo sed -i 's/^Current=.*/Current=omarchy/' "$f"
done
grep -Hn '^Current=' /etc/sddm.conf.d/* /etc/sddm.conf 2>/dev/null
sudo systemctl restart sddm
Every line the last grep prints must read Current=omarchy. A stray .pacnew or editor backup in /etc/sddm.conf.d/ is better deleted than edited, once you have checked it holds nothing else you need.
Plain Arch, or to keep a Qt5 theme on purpose: install the Qt5 runtime. The sddm package lists qt5-declarative as its optional dependency for Qt5 themes, and a greeter started under a Wayland compositor also needs the Qt5 Wayland platform plugin from qt5-wayland:
sudo pacman -S --needed qt5-declarative qt5-wayland
Do not add QtVersion=6 to the stock themes' metadata.desktop as a fix. Those files belong to the sddm package and an upgrade overwrites them, and the themes were written for Qt5, so nothing guarantees they load under the Qt6 greeter. The Arch wiki's advice to add QtVersion=6 is for the opposite case, a Qt6 theme that omits the key and fails with Library import requires a version.
Verify
sudo journalctl -b -u sddm | grep -E 'greeter|Qt5'
The log shows sddm-greeter-qt6 starting and the login screen appears.