This is my /var/log/sddm.log from an unsuccessful upstart: > [11:57:20.087] (II) DAEMON: Initializing... > [11:57:20.090] (II) DAEMON: Starting... > [11:57:20.090] (II) DAEMON: Logind interface found > [11:57:20.091] (II) DAEMON: Adding new display... > [11:57:20.091] (II) DAEMON: Loaded empty theme configuration > [11:57:20.092] (II) DAEMON: Xauthority path: "/run/sddm/xauth_LWFoRx" > [11:57:20.092] (II) DAEMON: Using VT 7 > [11:57:20.092] (II) DAEMON: Display server starting... > [11:57:20.092] (II) DAEMON: Writing cookie to "/run/sddm/xauth_LWFoRx" > [11:57:20.092] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -background > none -seat seat0 vt7 -auth /run/sddm/xauth_LWFoRx -noreset -displayfd 16 > [11:57:21.377] (II) DAEMON: Setting default cursor > [11:57:21.394] (II) DAEMON: Running display setup script > "/usr/share/sddm/scripts/Xsetup" > [11:57:21.395] (II) DAEMON: Display server started. > [11:57:21.395] (II) DAEMON: Socket server starting... > [11:57:21.395] (II) DAEMON: Socket server started. > [11:57:21.395] (II) DAEMON: Loaded empty theme configuration > [11:57:21.396] (II) DAEMON: Greeter starting... > [11:57:21.406] (II) HELPER: [PAM] Starting... > [11:57:21.406] (II) HELPER: [PAM] Authenticating... > [11:57:21.406] (II) HELPER: [PAM] returning. > [11:57:21.425] (II) HELPER: Writing cookie to "/tmp/xauth_ocMfUA" > [11:57:21.425] (II) HELPER: Starting X11 session: "" > "/usr/bin/sddm-greeter-qt6 --socket /tmp/sddm-:0-lMuEWF" > [11:57:21.426] (II) DAEMON: Greeter session started successfully > [11:57:21.468] (II) DAEMON: Message received from greeter: Connect
I think it looks pretty much the same as for a successful one... I peeked into ~/.local/share/sddm/wayland-session.log as well, but I got the impression that this starts getting written later (after having logged in)? Regards, Markus On Thu, Jan 30, 2025, at 09:06, Michael wrote: > On Wednesday 29 January 2025 21:19:50 Greenwich Mean Time Markus Gustafsson > wrote: >> Thanks for the input. I do indeed have a pretty new CPU as well. >> >> I did try the rc.conf trick but no luck after trying it once. I'll keep it >> around for a while and see if I can see an overall improvement. >> >> Regards, >> Markus > > If your SDDM problem were the same as mine, then my solution would have an > immediate and permanent effect. Have you looked at: > > ~/.local/share/sddm/xorg-session.log > > or, > > ~/.local/share/sddm/wayland-session.log > > and > > /var/log/sddm.log > > for any hints pointing to the cause of this? > Attachments: > * signature.asc
