| Post Reply | RetroFed Forum Forum Index » Linux |
| Author | Message | ||
|---|---|---|---|
ohshit604
sh.itjust.works
ohshit604@sh.itjust.worksJoined: 2025-02-08 |
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.
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? UpdateSo 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. |
||
| 13 Original | |||
|
just_another_person
lemmy.world
just_another_person@lemmy.world Joined: 2023-07-07 |
Change your time servers or add more to the load balanced con, and make sure you don't have a block on your network for those hosts. You can also set the timeout for that particular service to something shorter so it doesn't hang, or remove deps that rely on it from the service files. |
||
| 2 | |||
|
liking625
lemmy.world
liking625@lemmy.world Joined: 2025-11-24 |
i had some of that too, too many times with Debian 13, I ended up moving to Fedora to try and i dont have those problems any more. Mine would be some type of config corruption, making a new user it would log in fine,and deleting kde config files from my user would also let me log in instead of a black window. Also when shuting down some systemctl service would block the stopping 1 minute and 40 seconds or something similar because of some connection issue ( I do not remember the reason well enough to be precise). This made me decide to seek some other more stable desktop for the time being, and Fedora seems to just work all along. |
||
| 1 | |||
|
SayCyberOnceMore
feddit.uk
Cyber@feddit.uk Joined: 2023-06-17 |
Try Just as a reality check, disable systemd-timesyncd and verify if that is the problem - tbh, I'd be surprised it's that. There can be an issue with things like databases holding up the shutdown / reboot (I have an issue with a systemd service waiting for mariadb that I've not found time to resolve)... I don't use kde, but perhaps there's something there that might help point to the issue. |
||
| 1 | |||
|
non_burglar
lemmy.world
non_burglar@lemmy.world Joined: 2023-06-16 |
Can tell you about how long thing took to start, and the -blame flag can help pinpoint hangs and so on. |
||
| 1 | |||
|
Eggymatrix
sh.itjust.works
Eggymatrix@sh.itjust.works Joined: 2023-07-09 |
All these timers can be tweaked in the systemd confog file. In my lightweight testing VMs for example I set the kill after term to 3 seconds, instead of the default minute and a half. |
||
| 2 | |||
|
ohshit604
sh.itjust.works
ohshit604@sh.itjust.works Joined: 2025-02-08 |
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: 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. |
||
| 1 | |||
|
ohshit604
sh.itjust.works
ohshit604@sh.itjust.works Joined: 2025-02-08 |
Try journalctl -xe to get more info Just as a reality check, disable systemd-timesyncd and verify if that is the problem - tbh, I'd be surprised it's that. There can be an issue with things like databases holding up the shutdown / reboot (I have an issue with a systemd service waiting for mariadb that I've not found time to resolve)... I don't use kde, but perhaps there's something there that m...
Well that's interesting, I ran Appears to be related to my wallpaper, perhaps the KDE Wallpaper Engine plugin i use borked, however i never did mention in the main post but i did backup and reset my desktop environment following Debians documentation and that didn't resolve the hanging issue either so i am hesitant to say the desktop itself is borked, seems more like a dependency that's failing to talk with plasma. Edit: After doing some digging it appears others have encountered the same kwin error message along with comments of freezing and crashing. Appears to be a driver issue and is patched in 580.xx versions which Debian 13 does not ship on its stable branch. |
||
| 2 | |||
|
non_burglar
lemmy.world
non_burglar@lemmy.world Joined: 2023-06-16 |
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 de...
Ah, that is odd. The |
||
| 1 | |||
| Post Reply |
Back to top |