User Manager taking too long to shutdown

ItsFireStorm · 2025-09-24 21:54:23

I have had this problem for a while now and cannot seem to fix it other than to set a timeout limit to the service itself, digging through journal logs it contains stuff like my browser shutting down, Steam, among others which I would generally wait for them to shut down.

So it has come to a point that when I shut down my computer it takes ~1m 30s to shut down completely because of this.

My latest shutdown log: https://0x0.st/Kmph.txt

I'm worried to set the TimeoutStopSec option back in case it could corrupt cache, otherwise these are the current overrides I've set for user@1000.service

[Service]
# TimeoutStopSec = 10s
KillMode=control-group
SendSIGKILL=yes
KillUserProcesses=yes

Can someone help me track down the culprits and how to make them shut down faster?

c>rust · 2025-10-10 18:00:37

Sep 24 23:43:24 archbtw systemd[1]: Finished Tell Plymouth To Jump To initramfs.
Sep 24 23:44:04 archbtw kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:94:3c:96:40:a5:70:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
Sep 24 23:44:44 archbtw kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:94:3c:96:40:a5:70:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x80 TTL=1 ID=0 DF PROTO=2 
Sep 24 23:44:53 archbtw systemd[985]: Failed to query API bus instance ID, not deserializing subscriptions: Transport endpoint is not connected

I guess it have some thing to do with some weird internet filesystem
could you tell how the problem start to appear
you could try to kill and or disable UFW
or try to kill or umount online filesystem

$mount

Last edited by c>rust (2025-10-10 18:25:59)

seth · 2025-10-10 18:29:07

90s is a systemd service timeout and it smells like it's

Sep 24 23:38:13 archbtw wireplumber[930]: default: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
Sep 24 23:38:13 archbtw wireplumber[930]: wp-device: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
Sep 24 23:38:13 archbtw wireplumber[930]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.
Sep 24 23:38:21 archbtw wireplumber[1110]: default: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
Sep 24 23:38:21 archbtw wireplumber[1110]: wp-device: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
Sep 24 23:38:21 archbtw wireplumber[1110]: s-monitors-libcamera: PipeWire's libcamera SPA plugin is missing or broken. Some camera types may not be supported.
Sep 24 23:43:23 archbtw wireplumber[1110]: m-dbus-connection: <WpDBusConnection:0x559d05d10610> DBus connection closed: Underlying GIOStream returned 0 bytes on an async read
Sep 24 23:43:23 archbtw kernel: wireplumber[1110]: segfault at 8 ip 00007fabb57d8191 sp 00007fffa3dbaa18 error 4 in libgobject-2.0.so.0.8600.0[3a191,7fabb57aa000+37000] likely on CPU 3 (core 3, socket 0)
Sep 24 23:43:23 archbtw wireplumber[1110]: m-dbus-connection: <WpDBusConnection:0x559d05d10610> Trying to reconnect after core sync
Sep 24 23:43:23 archbtw systemd-coredump[10099]: Process 1110 (wireplumber) of user 1000 terminated abnormally with signal 11/SEGV, processing...
Sep 24 23:44:53 archbtw systemd[985]: wireplumber.service: Main process exited, code=dumped, status=11/SEGV
Sep 24 23:44:53 archbtw systemd[985]: wireplumber.service: Failed with result 'core-dump'.

so

Sep 24 23:43:23 archbtw wireplumber[1110]: m-dbus-connection: <WpDBusConnection:0x559d05d10610> DBus connection closed: Underlying GIOStream returned 0 bytes on an async read
Sep 24 23:43:23 archbtw kded6[1179]: org.kde.pulseaudio: context kaput
Sep 24 23:43:23 archbtw kded6[1179]: org.kde.pulseaudio: No object for name "effect_input.virtual-surround-7.1-hesuvi"
Sep 24 23:43:23 archbtw dbus-broker[1046]: Dispatched 23633 messages @ 3(±4)μs / message.
Sep 24 23:43:23 archbtw kded6[1179]: org.kde.pulseaudio: No object for name "effect_input.virtual-surround-7.1-hesuvi"
Sep 24 23:43:23 archbtw kernel: wireplumber[1110]: segfault at 8 ip 00007fabb57d8191 sp 00007fffa3dbaa18 error 4 in libgobject-2.0.so.0.8600.0[3a191,7fabb57aa000+37000] likely on CPU 3 (core 3, socket 0)
Sep 24 23:43:23 archbtw kded6[1179]: org.kde.pulseaudio: No object for name "effect_input.virtual-surround-7.1-hesuvi"
Sep 24 23:43:23 archbtw kernel: Code: 00 00 00 4c 89 ce e9 3e cc ff ff 0f 1f 00 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 85 ff 74 47 48 8b 07 48 85 c0 74 3f <48> 8b 00 48 3d fc 03 00 00 77 2c 48 8d 15 9d 3f 02 00 48 c1 e8 02
Sep 24 23:43:23 archbtw kded6[1179]: org.kde.pulseaudio: No object for name "rnnoise_source"

Bluetooth shuts down right before that - do you have any BT outputs (speakers, headphones,…)?

ItsFireStorm · 2025-10-11 12:53:06

No, I do not have any BT outputs currently, I usually use a controller but I didn't use it in this instance.

seth · 2025-10-11 13:10:52

Anything else that might stand out about your sound/wireplumber setup?
Do you also get this when first logging out and then shutting down from the DM?
(Could be something stupid like a logout tune…)

ItsFireStorm · 2025-10-11 16:17:05

I do have a Virtual Surround Sink setup that I use if that's ever worth mentioning, that's practically all that's modified from my sound setup.
I'm not sure that I have a logout tune, maybe the custom theme I installed for KDE Plasma comes with one but I never really heard it. Does the log say something about it that I could have missed?

seth · 2025-10-11 20:29:29

I do have a Virtual Surround Sink setup that I use if that's ever worth mentioning

Sep 24 23:43:23 archbtw kded6[1179]: org.kde.pulseaudio: No object for name "effect_input.virtual-surround-7.1-hesuvi"

It also shows up in the errors - so test to remove that and see whether wireplumber still crashes during the shutdown.

Arch Linux

#1 2025-09-24 21:54:23

User Manager taking too long to shutdown

#2 2025-10-10 18:00:37

Re: User Manager taking too long to shutdown

#3 2025-10-10 18:29:07

Re: User Manager taking too long to shutdown

#4 2025-10-11 12:53:06

Re: User Manager taking too long to shutdown

#5 2025-10-11 13:10:52

Re: User Manager taking too long to shutdown

#6 2025-10-11 16:17:05

Re: User Manager taking too long to shutdown

#7 2025-10-11 20:29:29

Re: User Manager taking too long to shutdown

Board footer