But not for me. After a reboot, it still hangs.Have you tried removing its configuration? It works for me so it can't be completely broken.
Here's the journalctl output for the latest attempt to start sddm
- this time with the truncated line included:
Jan 27
09:49:49 transponder systemd[1]: Started sddm.service - Simple
Desktop Display Manager.
Jan 27
09:49:49 transponder sddm[1590]: Initializing...
Jan 27
09:49:49 transponder sddm[1590]: Starting...
Jan 27
09:49:49 transponder sddm[1590]: Logind
interface found
Jan 27
09:49:49 transponder sddm[1590]: Adding new
display...
Jan 27
09:49:49 transponder sddm[1590]: Loaded empty
theme configuration
Jan 27
09:49:49 transponder sddm[1590]: Xauthority
path: "/run/sddm/xauth_QcqrjQ"
Jan 27
09:49:49 transponder sddm[1590]: Using VT 2
Jan 27
09:49:49 transponder sddm[1590]: Display server
starting...
Jan 27
09:49:49 transponder sddm[1590]: Writing cookie
to "/run/sddm/xauth_QcqrjQ"
Jan 27
09:49:49 transponder sddm[1590]: Running:
/usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -au
th /run/sddm/xauth_QcqrjQ -noreset -displayfd 16
Jan 27
09:49:49 transponder sddm[1590]: Failed
to read display number from pipe
Jan 27
09:49:49 transponder sddm[1590]: Display server
stopping...
Jan 27
09:49:49 transponder sddm[1590]: Attempt
1 starting the Display server on vt 2 failed