Upgrading from 6.11.10-amd64 to 6.12.3 and now 6.12.5 is throwing the following error in SDDM and refusing to start a graphical interface. Virtual terminal login remains fine, and rebooting back to the 6.11.10 kernel brings the login screen up as expected. KDE would be running Wayland, but looks like SDDM still wants to use X, and I'm not sure if that's a problem or not.
Any suggestions appreciated!
SDDM has no custom config and has 'just worked' up until installing the 6.12 kernel. I've seen some suggestion about changing SDDM to use Wayland, but having tried this using this config:Dec 20 07:21:03 mosscap sddm[1071]: Failed to read display number from pipe
Dec 20 07:21:03 mosscap sddm[1071]: Display server stopping...
Dec 20 07:21:03 mosscap sddm[1071]: Attempt 1 starting the Display server on vt 2 failed
Dec 20 07:21:05 mosscap sddm[1071]: Display server starting...
Dec 20 07:21:05 mosscap sddm[1071]: Writing cookie to "/run/sddm/xauth_CPQYBN"
Dec 20 07:21:05 mosscap sddm[1071]: Running: /usr/bin/X -dpi 0 -background none -seat seat0 vt2 -auth /run/sddm/xauth_CPQYBN -noreset -displayfd 16
Dec 20 07:21:06 mosscap sddm[1071]: Failed to read display number from pipe
Dec 20 07:21:06 mosscap sddm[1071]: Display server stopping...
Dec 20 07:21:06 mosscap sddm[1071]: Attempt 2 starting the Display server on vt 2 failed
Dec 20 07:21:08 mosscap sddm[1071]: Display server starting...
Dec 20 07:21:08 mosscap sddm[1071]: Writing cookie to "/run/sddm/xauth_CPQYBN"
Dec 20 07:21:08 mosscap sddm[1071]: Running: /usr/bin/X -dpi 0 -background none -seat seat0 vt2 -auth /run/sddm/xauth_CPQYBN -noreset -displayfd 16
Dec 20 07:21:09 mosscap sddm[1071]: Failed to read display number from pipe
Dec 20 07:21:09 mosscap sddm[1071]: Display server stopping...
Dec 20 07:21:09 mosscap sddm[1071]: Attempt 3 starting the Display server on vt 2 failed
Dec 20 07:21:09 mosscap sddm[1071]: Could not start Display server on vt 2
Dec 20 07:23:25 mosscap systemd[1]: Stopping sddm.service - Simple Desktop Display Manager...
Dec 20 07:23:25 mosscap sddm[1071]: Signal received: SIGTERM
Dec 20 07:23:25 mosscap systemd[1]: sddm.service: Deactivated successfully.
SDDM then starts, but goes no further than black screen with flashing cursor and the logs now show:/etc/sddm.conf.d/10-wayland.conf
[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell
[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1
So I'm back on the previous kernel with working GUI, but would be nice to be able to update at some point. Am I missing anything obvious here? It looks like this is a recurring issue searching around for it, but a lot of the suggestions like switching to wayland for SSDM and making sure relevant nvidia modules are loaded haven't yet fixed it.Dec 20 07:24:01 mosscap sddm-helper[1428]: Starting Wayland user session: "/etc/sddm/wayland-session" "/usr/lib/x86_64-linux-gnu/libexec/plasma-dbus-run-sess>
Dec 20 07:24:02 mosscap sddm[1063]: Session started true
Dec 20 07:24:02 mosscap sddm-helper[1428]: Failed to write utmpx: No such file or directory
Dec 20 14:09:46 mosscap sddm[1063]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Dec 20 14:09:46 mosscap sddm[1063]: Auth: sddm-helper (--socket /tmp/sddm-auth-0ed8f4d7-ebc4-46df-9155-533016df2888 --id 1 --start /usr/lib/x86_64-linux-gnu/>
Dec 20 14:09:46 mosscap sddm[1063]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Dec 20 14:09:46 mosscap sddm[1063]: Auth: sddm-helper exited with 1
Dec 20 14:09:46 mosscap sddm[1063]: Signal received: SIGTERM
Any suggestions appreciated!
Statistics: Posted by antigone — 2024-12-20 14:19 — Replies 0 — Views 14