Arch Linux

traxx2012

Member

Registered: 2025-04-14

Posts: 3

[SOLVED] Shutdown hangs at "reboot: Power down"

When shutting down my system (I usually use `shutdown now`), it sometimes hangs at:

[timestamp]: reboot: Power down

and nothing else on screen.
USB devices are powered down by then so I couldn't try any key combination to try and get more output.

This is the output of  `journalctl -k -b -1`, everything before this block was hours earlier (full log here).

Apr 14 02:49:26 base3-arch kernel: xdg-desktop-por[1760]: segfault at 64 ip 00007bef149d388c sp 00007ffe1ba6a760 error 6 in libwayland-client.so.0.23.1[588c,7bef149d1000+6000] likely on CPU 3 (core 3, socket 0)
Apr 14 02:49:26 base3-arch kernel: Code: c3 00 00 00 01 81 fb 00 00 f0 00 77 61 49 8b 04 24 48 c1 e8 03 39 d8 72 65 39 c3 74 21 49 8b 44 24 10 43 8d 54 2d 00 48 09 d1 <48> 89 0c d8 31 c0 48 83 c4 18 5b 41 5c 41 5d 5d c3 0f 1f 00 48 89
Apr 14 02:49:28 base3-arch kernel: EXT4-fs (dm-8): unmounting filesystem 9adc9d55-9126-4b77-be5e-fc365ca1da8d.
Apr 14 02:49:28 base3-arch kernel: EXT4-fs (dm-9): unmounting filesystem e264cbb3-e077-4f47-a914-7d9ee7a97390.
Apr 14 02:49:28 base3-arch kernel: EXT4-fs (dm-10): unmounting filesystem 326ad2a4-e53b-44f4-bee1-fa63cf04c8f3.
Apr 14 02:49:29 base3-arch kernel: EXT4-fs (dm-11): unmounting filesystem 02a214c0-3372-4095-b8a3-321181dd85fb.
Apr 14 02:49:30 base3-arch systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 14 02:49:30 base3-arch systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 14 02:49:30 base3-arch systemd-journald[527]: Received SIGTERM from PID 1 (systemd-shutdow).

As far as I understand it, the only really interesting line is the segfault from some xdg-desktop-portal-?. This truncation is not very helpful, as I don't know which specific application is at fault.
I don't know what to make of that kernel: Code: line and googling for it nets me the Linux source.

Edit: after thinking about it for a while, I'm somewhat sure the default is a red herring in this case. Since the file systems get unmounted and USB powers off, I don't think some userland application can mess things up this far down the line. It's more likely to be something way lower in the system architecture not being able to cut power correctly.

Installed portals:

• xdg-desktop-portal-gtk

• xdg-desktop-portal-hyprland

This is the system setup, in case anything becomes relevant:

• NVIDIA RTX3050 via nvidia-dkms

• LUKS over LVM

• systemd-boot

• display manager: ly

• window manager: hyprland

The most annoying part is that it works most of the time but not all of the time. This makes testing things a nightmare.
For the moment, I'm shutting the system down at that point by holding the power button down (which seems safe enough as all FSs are unmounted prior to that) but it's far from ideal.

Last edited by traxx2012 (2025-05-06 00:58:17)

espresso

Member

From: Pale Blue Dot, US

Registered: 2023-05-15

Posts: 50

Re: [SOLVED] Shutdown hangs at "reboot: Power down"

Based on this very similar configuration and same Hyprland version with backtrace - https://gitlab.freedesktop.org/wayland/ … issues/513 - If I had to guess, Hyprland is accessing a wl_resource from one thread while another thread destroys it (though I'm not sure why it's posted in Wayland, but Hyprland repo does not seem to allow user issue posts). or perhaps a mishandling between components.
Perhaps an issue with cleanup of file dialog or screen sharing? As Wayland compositors mature, these things should be less common.

Last edited by espresso (2025-04-16 15:08:24)

traxx2012

Member

Registered: 2025-04-14

Posts: 3

Re: [SOLVED] Shutdown hangs at "reboot: Power down"

Reporting back: I tried shutting down with 'shutdown -P now' (the interesting part being the flag) and had no issues for a few days, but just now it didn't fully shut down again.
I'm out of ideas again.

traxx2012

Member

Registered: 2025-04-14

Posts: 3

Re: [SOLVED] Shutdown hangs at "reboot: Power down"

I've had no issues shutting down for quite a while now. Either the shutdown -P did something after all or a kernel update solved it.