No longer powers off

Powering off no longer shuts down the computer, both with the latest kernel and the latest LTS kernel.

The screen goes blank, and that's all folks. The tower stays on.

  • Channel: Stable
  • Graphics card: Radeon HD5870
  • Graphic drivers: Mesa
  • Desktop environment: Deepin

By now you should know how to provide more than the barest minimal system info and a 'it doesnt work' .. how about an inxi, or maybe what you've tried already?
Does this happen no matter how you try to shut down ?
Or is it just through the desktop buttons?
Have you tried systemctl poweroff ?

1 Like


Actually I don't know where to begin. As when that happened in the past it was always the kernel, and if it was simply a process on hold I think the screen won't go off without showing any systemd error.

Lets see...

Yeah, those fail to.

Perhaps in the init logs...

I assume you probably tried this but does sudo shutdown now or sudo reboot work?
Also, check you're kernel logs see what it does when you attempt those commands

The cause seems to be udev crashing due to a printer driver misbehaving:

hp[649]: io/hpmud/pp.c 627: unable to read device-id ret=-1
python[653]: io/hpmud/pp.c 627: unable to read device-id ret=-1
systemd-coredump[678]: Process 401 (udev-configure-) of user
0 dumped core.
Stack trace of thread 401:
#0  0x00007f4cc8611f25 raise (
#1  0x00007f4cc85fb897 abort (
#2  0x00007f4cc8655258 __libc_message (
#3  0x00007f4cc865c77a malloc_printerr (
#4  0x00007f4cc865e14c _int_free (
#5  0x0000563c9e4e3ccd n/a (udev-configure-printer)
#6  0x0000563c9e4e4a58 n/a (udev-configure-printer)
#7  0x0000563c9e4e210a n/a (udev-configure-printer)
#8  0x00007f4cc85fd153 __libc_start_main (
#9  0x0000563c9e4e23ee n/a (udev-configure-printer)

Could you try disabling your printer with systemctl? Also, does this happen every time?

Another thing I'm curious about is should it really have the privileges to stop your computer from shutting down or is something hanging in the drivers constantly?

It looks like the printer makes udev to crash, which is in charge of shutting down the system.

I will try disabling some printer goodies :cookie:

The printer drivers weren't the problem, as uninstalling them makes the crash to disappear from the logs but the system still doesn't power off.

Log before reboot

I tried changing mkinitcpio hooks from systemd to udev without success.

HOOKS="base systemd keyboard sd-vconsole autodetect modconf
block filesystems"
HOOKS="base udev autodetect modconf block keyboard keymap
resume filesystems fsck"

Something is fckd up with latest update. I have same problem with xfce (and reported it twice to the update thread). Tried different kernels (4.19, 5.2, 5.3) also tried adding shutdown hook but nothing helps... Prior to update had no problems whatsoever

System:    Host: NAS Kernel: 5.3.5-1-MANJARO x86_64 bits: 64 Desktop: Xfce 4.14.1 Distro: Manjaro Linux 
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <root required> 
           Mobo: Gigabyte model: F2A88X-D3H v: x.x serial: <root required> UEFI: American Megatrends v: F4 
           date: 01/08/2014 
CPU:       Dual Core: AMD A6-7400K Radeon R5 6 Compute Cores 2C+4G type: MCP speed: 2538 MHz min/max: 1400/3500 MHz 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R5 Graphics] driver: radeon v: kernel 
           Device-2: NVIDIA GK107 [GeForce GTX 650] driver: nvidia v: 435.21 
           Display: x11 server: X.Org 1.20.5 driver: nvidia resolution: 1920x1080~60Hz, 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 650/PCIe/SSE2 v: 4.6.0 NVIDIA 435.21 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
Drives:    Local Storage: total: 7.22 TiB used: 6.10 TiB (84.4%) 
Info:      Processes: 173 Uptime: 1h 13m Memory: 6.80 GiB used: 1.66 GiB (24.4%) Shell: bash inxi: 3.0.36 



So what did you do ?

Nothing, an update resulted in a fix.

Latest stable update 2019-11-14 fixed problem for me. Reboot and power-off works again. I just wished someone looked into this and figured out what exactly was broken so this type of random bugs doesn't repeat.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by