I don't run haveged, but I think you might be on to something regarding the entropy... Googling around shows a lot of people having similar issues. I'm gonna try out haveged and see if it improved the situation.
On Sun, Feb 2, 2025, at 14:11, Michael wrote: > On Sunday 2 February 2025 11:09:09 Greenwich Mean Time Markus Gustafsson > wrote: >> 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... > > There's more happening after this stage with a successful login. > > The daemon will register a login received from the greeter and the helper > will > negotiate authentication for the desktop session with PAM, then the helper > will launch a X11 or Wayland desktop session. However, if you have no GUI > display coming up to enter your password, the process will stop where you > have > arrived at above. > > Have you set up your haveged service to start at boot? > > I don't know if enabling any crypto co-processors available on the MoBo or > CPU > in the BIOS and in your kernel may make a difference. My SDDM problem was > related to having enough entropy available when SDDM was launching too soon > in > the boot up process. > > >> 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)? > > Yes, this would take place once a desktop session has been set up. I can't > recall if you may see some errors in there in cases when SDDM does not > shutdown and crashes. > Attachments: > * signature.asc
