systems halts, but does not power off

Started by finotti, 2026/06/30, 13:50:52

Previous topic - Next topic

finotti

Using Plasma/SDDM on X11, after a recent upgrade, when I ask the system to shut down, the system halts, but it does not power off: the lights remain on and the fans continue to spin, even though the system/software is off.
If I run the command (systemclt poweroff) from the command line, it works (i.e., it does power off).  Is anyone else experiencing the same?  Any ideas or suggestions?
Some info about the system:
$ inxi -v4
System:
  Host: debian Kernel: 7.1.2-1-siduction-amd64 arch: x86_64 bits: 64
    compiler: gcc v: 15.3.0
  Desktop: KDE Plasma v: 6.6.5 Distro: siduction 2024.1.0 shine-on - kde -
    (202412261719) base: Debian GNU/Linux forky/sid
Machine:
  Type: Desktop System: Micro-Star product: MS-7E51 v: 1.0
    serial: <superuser required>
  Mobo: Micro-Star model: MAG X870 TOMAHAWK WIFI (MS-7E51) v: 1.0
    serial: <superuser required> Firmware: UEFI vendor: American Megatrends LLC.
    v: 1.A71 date: 01/13/2026
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
    charge: 55% (should be ignored) status: discharging
CPU:
  Info: 8-core model: AMD Ryzen 7 9700X bits: 64 type: MT MCP arch: Zen 5
    rev: 0 cache: L1: 640 KiB L2: 8 MiB L3: 32 MiB
  Speed (MHz): avg: 605 min/max: 605/5582 boost: enabled cores: 1: 605
    2: 605 3: 605 4: 605 5: 605 6: 605 7: 605 8: 605 9: 605 10: 605 11: 605
    12: 605 13: 605 14: 605 15: 605 16: 605 bogomips: 121599
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
    ssse3 svm
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 23 [Radeon RX 6600/6600
    XT/6600M] vendor: ASRock driver: amdgpu v: kernel arch: RDNA-2
    bus-ID: 03:00.0
  Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
    vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-2 bus-ID: 74:00.0
    temp: 36.0 C
  Device-3: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB
    bus-ID: 5-2.3.2:6
  Display: x11 server: X.Org v: 21.1.23 with: Xwayland v: 24.1.12 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi
    gpu: amdgpu resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz
  API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.2-1 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon RX 6600 (radeonsi navi23 ACO DRM
    3.64 7.1.2-1-siduction-amd64)
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: amdgpu_top wl: wayland-info
    x11: xdriinfo, xdpyinfo, xprop, xrandr
Network:
  Device-1: Qualcomm WCN785x Wi-Fi 7 320MHz 2x2 [FastConnect 7800]
    vendor: Foxconn Band Simultaneous Wireless driver: ath12k_wifi7_pci v: N/A
    bus-ID: 09:00.0
  IF: wlan0 state: up mac: ac:f2:3c:22:da:a3
  Device-2: Realtek RTL8126 5GbE vendor: Micro-Star MSI driver: r8169
    v: kernel port: e000 bus-ID: 0a:00.0
  IF: enp10s0 state: up speed: 100 Mbps duplex: full mac: 34:5a:60:03:0a:a5
  IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Drives:
  Local Storage: total: 19.1 TiB used: 7.11 TiB (37.2%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 990 EVO Plus 4TB
    size: 3.64 TiB temp: 27.9 C
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 990 EVO 2TB size: 1.82 TiB
    temp: 31.9 C
  ID-3: /dev/sda vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB
  ID-4: /dev/sdb vendor: Crucial model: CT2000MX500SSD1 size: 1.82 TiB
  ID-5: /dev/sdc vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB
  ID-6: /dev/sdd vendor: Seagate model: ST8000VN004-3CP101 size: 7.28 TiB
Partition:
  ID-1: / size: 3.57 TiB used: 978.07 GiB (26.7%) fs: ext4 dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 472 KiB (0.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: swap-1 size: 8.8 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p3
Info:
  Memory: total: 60 GiB note: est. available: 60.38 GiB used: 6.85 GiB (11.3%)
  Processes: 607 Uptime: 6m Init: systemd
  Packages: 5255 Compilers: clang: 21.1.8 gcc: 15.3.0 Shell: Bash v: 5.3.9
    inxi: 3.3.40

batonweepy

Quote from: finotti on 2026/06/30, 13:50:52Using Plasma/SDDM on X11, after a recent upgrade, when I ask the system to shut down, the system halts, but it does not power off: the lights remain on and the fans continue to spin, even though the system/software is off.
If I run the command (systemclt poweroff) from the command line, it works (i.e., it does power off).  Is anyone else experiencing the same?  Any ideas or suggestions?
Some info about the system:
$ inxi -v4
System:
  Host: debian Kernel: 7.1.2-1-siduction-amd64 arch: x86_64 bits: 64
    compiler: gcc v: 15.3.0
  Desktop: KDE Plasma v: 6.6.5 Distro: siduction 2024.1.0 shine-on - kde -
    (202412261719) base: Debian GNU/Linux forky/sid
Machine:
  Type: Desktop System: Micro-Star product: MS-7E51 v: 1.0
    serial: <superuser required>
  Mobo: Micro-Star model: MAG X870 TOMAHAWK WIFI (MS-7E51) v: 1.0
    serial: <superuser required> Firmware: UEFI vendor: American Megatrends LLC.
    v: 1.A71 date: 01/13/2026
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M510
    charge: 55% (should be ignored) status: discharging
CPU:
  Info: 8-core model: AMD Ryzen 7 9700X bits: 64 type: MT MCP arch: Zen 5
    rev: 0 cache: L1: 640 KiB L2: 8 MiB L3: 32 MiB
  Speed (MHz): avg: 605 min/max: 605/5582 boost: enabled cores: 1: 605
    2: 605 3: 605 4: 605 5: 605 6: 605 7: 605 8: 605 9: 605 10: 605 11: 605
    12: 605 13: 605 14: 605 15: 605 16: 605 bogomips: 121599
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
    ssse3 svm
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Navi 23 [Radeon RX 6600/6600
    XT/6600M] vendor: ASRock driver: amdgpu v: kernel arch: RDNA-2
    bus-ID: 03:00.0
  Device-2: Advanced Micro Devices [AMD/ATI] Granite Ridge [Radeon Graphics]
    vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-2 bus-ID: 74:00.0
    temp: 36.0 C
  Device-3: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB
    bus-ID: 5-2.3.2:6
  Display: x11 server: X.Org v: 21.1.23 with: Xwayland v: 24.1.12 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi
    gpu: amdgpu resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz
  API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.2-1 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon RX 6600 (radeonsi navi23 ACO DRM
    3.64 7.1.2-1-siduction-amd64)
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: amdgpu_top wl: wayland-info
    x11: xdriinfo, xdpyinfo, xprop, xrandr
Network:
  Device-1: Qualcomm WCN785x Wi-Fi 7 320MHz 2x2 [FastConnect 7800]
    vendor: Foxconn Band Simultaneous Wireless driver: ath12k_wifi7_pci v: N/A
    bus-ID: 09:00.0
  IF: wlan0 state: up mac: ac:f2:3c:22:da:a3
  Device-2: Realtek RTL8126 5GbE vendor: Micro-Star MSI driver: r8169
    v: kernel port: e000 bus-ID: 0a:00.0
  IF: enp10s0 state: up speed: 100 Mbps duplex: full mac: 34:5a:60:03:0a:a5
  IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
Drives:
  Local Storage: total: 19.1 TiB used: 7.11 TiB (37.2%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 990 EVO Plus 4TB
    size: 3.64 TiB temp: 27.9 C
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 990 EVO 2TB size: 1.82 TiB
    temp: 31.9 C
  ID-3: /dev/sda vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB topgames
  ID-4: /dev/sdb vendor: Crucial model: CT2000MX500SSD1 size: 1.82 TiB
  ID-5: /dev/sdc vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB
  ID-6: /dev/sdd vendor: Seagate model: ST8000VN004-3CP101 size: 7.28 TiB
Partition:
  ID-1: / size: 3.57 TiB used: 978.07 GiB (26.7%) fs: ext4 dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 299.4 MiB used: 472 KiB (0.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: swap-1 size: 8.8 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p3
Info:
  Memory: total: 60 GiB note: est. available: 60.38 GiB used: 6.85 GiB (11.3%)
  Processes: 607 Uptime: 6m Init: systemd
  Packages: 5255 Compilers: clang: 21.1.8 gcc: 15.3.0 Shell: Bash v: 5.3.9
    inxi: 3.3.40


systemctl poweroff working means hardware + systemd are OK. This is likely Plasma/SDDM not calling the same poweroff path after the update. Check
systemd-logind and Plasma/PowerDevil logs first. Might be a KDE regression.

Geier0815

I think it's not only KDE as I have similar problems with XFCE also with x11. It's not every shutdown but 2 out of 3.
Wenn Windows die Lösung ist...
kann ich dann bitte das Problem zurück haben?

finotti

#3
Quote from: batonweepy on 2026/07/01, 09:25:54systemctl poweroff working means hardware + systemd are OK. This is likely Plasma/SDDM not calling the same poweroff path after the update. Check
systemd-logind and Plasma/PowerDevil logs first. Might be a KDE regression.
SDDM has the command systemctl poweroff set for shutdown, so it should be using it.  And I could not find any errors in the logs, but I will try to look more carefully.
But I noticed that when I issued "systemctl poweroff" from within a plasma session (in a konsole), it also did not work...  So, I am not sure when the command works or not 100%.  (When plasma is running?  When someone is logged in?  It is just random?)

scholle1

Quote:
But I noticed that when I issued "systemctl-poweroff" from within a plasma session (in a konsole), it also did not work...

This is wrong:
systemctl-poweroff
better
systemctl poweroff
"Pax in terris" - Das ist mein großer, mein einzigster für diese Welt von Herzen kommender Wunsch.
"Friede auf Erden" und alles Weitere erscheint einfach.

finotti

Quote from: scholle1 on 2026/07/02, 13:28:19
Quote:
But I noticed that when I issued "systemctl-poweroff" from within a plasma session (in a konsole), it also did not work...

This is wrong:
systemctl-poweroff
better
systemctl poweroff
Thanks for pointing it out.  They were typos.  I actually used the correct commands when I tried them.   I fixed the typos above.

dibl

If you will boot to runlevel 3, or change from plasma to runelevel 3 (the multi-user.target), shut down runlevel 5, and THEN issue the
systemctl poweroff it will reveal whether the problem lies in the sddm/X11 session, or deeper.
System76 Oryx Pro, Intel Core i7-11800H, ASRock B860 Pro-A, Intel Core Ultra 7 265KF, Nvidia GTX-1060, SSD 990 EVO Plus.

finotti

Firstly, thanks for the replies!
Quote from: RebeccaHong on 2026/07/16, 13:47:19That usually points to an ACPI or power management issue rather than the shutdown process itself. I'd also check whether the behavior is the same with a newer kernel and make sure the BIOS/UEFI firmware is up to date. Looking through the logs right before shutdown might also reveal an ACPI-related error that explains why it halts but never actually powers off.
I don't think that that is the problem.  I've just booted to Debian Stable and the shutdown worked as expected.

Quote from: dibl on 2026/07/16, 14:03:20If you will boot to runlevel 3, or change from plasma to runelevel 3 (the multi-user.target), shut down runlevel 5, and THEN issue the
systemctl poweroff it will reveal whether the problem lies in the sddm/X11 session, or deeper.

Thanks for the suggestion.  I will give it a try.

gnasch

My thinkpad T61 type 6463A13 is also affected by this. I ran a little test series:

When booting into init 3 (attach 3 at last position of linux boot line)
the following work impeccably:
systemctl suspend, shutdown, hibernate.

When booting into sddm, but not starting kde,
pressing the suspend, shutdown, hibernate icons on sddm screen,
they will all hang, producing heat and running the fan.
They then need a power off reset to come out of it.

The same behaviour happens when issuing the systemctl commands
from within konsole in kde.

When booting into sddm, then opening vty3 (ctrl-alt-F3)
the commands systemctl suspend, shutdown, hibernate will all work,
and the system will properly reduce energy consumption / shut off.
It can then be activated properly again.

What is the cause of this annoying behaviour?
thx, gnasch

finotti

#9
I think I figured it out, but need more tests.  I think the problem was the changes I made when the virtual consoles stopped working.  towo had a post to fix it, but then an official fix came and I never reverted those commands that towo suggested. . I did it today and I think that the problem is fixed .

EDIT: No, it did not work. 🙁  It seems that there is some randomness, as the computer did turn off once (after logging in KDE and shutting down from there), but not at the end of the day.

gnasch

I have since learnt, that after using kde for some time, the shutdown or hibernate from vty3 does not work any more. It also will hang when trying to shut the system off.