this post was submitted on 15 Sep 2025
36 points (97.4% liked)
Linux
59302 readers
481 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What's in the log?
I'm not familiar with using logs but looking at them now and filtering for the word 'failed', most of the entries around shutdown contain "dbus-daemon[1248]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down."
There are also a couple of "fwupd[2375]: 17:22:25.596 FuPluginUpower failed to query lid state"
And one of these: "NetworkManager[1332]: [1757956947.0782] dispatcher: (51) failed (after 0.004 sec): Refusing activation, D-Bus is shutting down."
Does any of that shed light on the problem?
That's just saying that things are tripping each other up whilst trying to shutdown.
Try
sudo journalctl -b-1 --reverseThat will show the last system log in reverse order, and might help see what's going on.
There's an old bug report (notice I say report, as it's locked and not solved - & I don't have the link to hand) with several people saying that systemd causes this, but, it might be applications or services that have user accounts open, etc, etc...
but... try shutting down services and unmounting any shares / filesystems that might be causing this to see if you can isolate something.
As mentioned in the other thread, try shutting down from the command line on a new TTY (text-only screen) and see if that shows anything else.