My system is running Debian 13, and has been running Debian great for well over a year however, recently when I went to reboot my computer KDE Plasma (X11) froze and didn’t want to log in, I found it odd and rebooted as per usual but it repeated itself yet again.

I jump into another TTY and start checking the journal, nothing out of the ordinary, obviously annoyed I start reinstalling packages.

kde-full, kde-standard, kde-plasma-desktop, sddm, nvidia-driver, linux-generic-headers xorg and so on. No luck. I figured I would give Wayland a try even though a lot of my software still does not support it, and to my surprise loaded up instantly, so I got some hope my system isn’t borked, I tried X11 again but instead of rebooting or shutting down after it froze I just left it to see if anything at all changes and after a while it decided to load my desktop!

So after a few more days of trying to catch something in my journal I finally noticed this 3 minute gap in these entries of my journal.

3/23/26 9:44 PM systemd systemd-timedated.service: Deactivated successfully. 3/23/26 9:45 PM systemd-timesyncd Timed out waiting for reply from 84.16.67.12:123 (2.debian.pool.ntp.org). 3/23/26 9:45 PM systemd-timesyncd Contacted time server 217.147.208.1:123 (2.debian.pool.ntp.org). 3/23/26 9:48 PM systemd Reload requested from client PID 2681 (‘startplasma-x11’)… 3/23/26 9:48 PM systemd Reloading…

I don’t have much to work off of but I’m guess this is what is kicking my system back in order, is there a way I could reduce the timeout of the above systemd request?


Update

So i manage to capture the time it takes for me to reboot and land back at my desktop, it’s roughly ~30 seconds to reboot and land at sddm but another whopping 5-6 minutes to actually load the X11 desktop.

I captured the logs within this time frame to hopefully weed out the issue I’m encountering.

Log File (via CopyParty)

  • ohshit604@sh.itjust.worksOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    14 hours ago

    systemd-analyze Can tell you about how long thing took to start, and the -blame flag can help pinpoint hangs and so on.

    I ran this command the output is as such:

    Startup finished in 7.208s (firmware) + 2.336s (loader) + 3.601s (kernel) + 15.279s (userspace) = 28.426s 
    graphical.target reached after 15.279s in userspace.
    

    Which is weird, i timed how long it took from rebooting to landing at the desktop and i got between 5-6 minutes, 30 seconds to reboot and land at SDDM but another 4.5-5 minutes actually loading the desktop itself.

    • non_burglar@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      10 hours ago

      Ah, that is odd. The systemd-analyze -blame command would break down all the systemd services by time, but if the delay is before or after the systemd startup process, dmesg or system logs should give you some hints about what is taking so long.