this post was submitted on 24 Mar 2026

10 points (100.0% liked)

Linux

64059 readers

722 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

[Help] Reduce timeout on services that hang for systemd (sh.itjust.works)

submitted 1 day ago* (last edited 17 hours ago) by ohshit604@sh.itjust.works to c/linux@lemmy.ml

8 comments fedilink hide all child comments

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)

top 8 comments

sorted by: hot top controversial new old

[–] Eggymatrix@sh.itjust.works 2 points 20 hours ago

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.

[–] non_burglar@lemmy.world 1 points 1 day ago (1 children)

systemd-analyze

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

[–] ohshit604@sh.itjust.works 1 points 17 hours ago* (last edited 17 hours ago) (1 children)

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 1 points 13 hours ago* (last edited 13 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.

[–] just_another_person@lemmy.world 2 points 1 day ago* (last edited 1 day ago)

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.

[–] Cyber@feddit.uk 1 points 1 day ago (1 children)

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 might help point to the issue.

[–] ohshit604@sh.itjust.works 2 points 17 hours ago* (last edited 13 hours ago)

Well that's interesting,

I ran journalctl -xe expecting not to get much of an output however, my log is full of:

Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: 0x501: GL_INVALID_VALUE error generated. <levels>, <width> and <height> must be 1 or greater.
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Mar 24 16:50:37 debian kwin_x11[2914]: kwin_effect_blur: Failed to create an offscreen framebuffer
Mar 24 17:00:00 debian systemd[2614]: Started drkonqi-sentry-postman.service - Submitting pending crash events.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ 
░░ A start job for unit UNIT has finished successfully.
░░ 
░░ The job identifier is 4486.
Mar 24 17:00:00 debian drkonqi-sentry-postman[9023]: org.kde.drkonqi.sentry: QNetworkReply::ConnectionRefusedError "Connection refused"
Mar 24 17:00:00 debian drkonqi-sentry-postman[9023]: org.kde.drkonqi.sentry: QNetworkReply::ConnectionRefusedError "Connection refused"
Mar 24 17:00:00 debian drkonqi-sentry-postman[9023]: org.kde.drkonqi.sentry: QNetworkReply::ConnectionRefusedError "Connection refused"
Mar 24 17:00:00 debian drkonqi-sentry-postman[9023]: org.kde.drkonqi.sentry: QNetworkReply::ConnectionRefusedError "Connection refused"
Mar 24 17:00:00 debian drkonqi-sentry-postman[9023]: org.kde.drkonqi.sentry: QNetworkReply::ConnectionRefusedError "Connection refused"
Mar 24 17:04:12 debian plasmashell[2938]: KPackageStructure of KPluginMetaData(pluginId:"org.kde.merkuro.contact.applet", fileName: "/usr/share/plasma/plasmoids/org.kde.merkuro.contact>
Mar 24 17:04:13 debian kmenuedit[3266]: QThreadStorage: Thread 0x55c784c1f8d0 exited after QThreadStorage 8 destroyed
Mar 24 17:04:13 debian systemd[2614]: app-org.kde.kmenuedit@c3c9752c88b040738079b63d23e609ee.service: Consumed 3.486s CPU time, 34.4M memory peak.

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.

[–] liking625@lemmy.world 1 points 1 day ago

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.