The system does not shut down

ddtty · October 22, 2023, 1:49pm

#  telinit 3
#  shutdown -h now

I have tried this under run level 1 (Ctrl+Alt-F1).
Unfortunately, with no luck.

Michele · October 22, 2023, 2:44pm

I found this modification to do on a forum. Now it marks. But I don’t know if it is because of this modification, or if last night it didn’t turn off for some casua and today instead it went well.

/etc/systemd/user.conf:


DefaultTimeoutStopSec=5s
DefaultTimeoutAbortSec=5s

mrmazda · October 22, 2023, 6:22pm

That’s a workaround I’ve used with 7s, but not a fix. Whatever is failing to exit should be found and a real fix applied. Identifying it may require filing a bug report.

karlmistelberger · October 23, 2023, 5:06am

At a first glance this looks fine.

To make sure you need to compare the Stopped list to the Started list and check for non-matching items.
You may logout from the KDE session and shut down using button of the display manager. Does this work?

ddtty · October 23, 2023, 10:52am

Oka~

For my issue, I think it might relate to my malfunction NVIDIA card.

This is a old laptop (bought around 2011) with both integrated intel and NVIDIA graphic card. After installing the propitiate NVIDIA driver, I found that each time doing

prime-select nvidia

after the re-login caused the system overheat and triggered the emergence power cut-off. And with propitiate NVIDIA driver installed, this laptop can not shutdown properly as the situation similar to the OP.

However, if I turn the graphical driver back to the nouveau, my laptop can shutdown though it took more than 10min to virtually cut off the power after the screen turning black.

So I think it is the hardware problem.

Michele · October 23, 2023, 10:57am

I came to the same conclusion myself during this night. Every time I set prime to nvidia the pc would not shut down. So this morning I switched prime back to intel, anyway the flatpak applications are set to work with the nvidia graphics driver. Then for the system ones if I am not mistaken there is prime-run a way to run them with the driver, but I don’t know if it is necessary. Maybe not. Anyway it will definitely shut down tonight.

Well…I hope not so definitively

Michele · October 23, 2023, 9:38pm

Exit the session and then turn off from the display manager, I had also tried. No, It won’t shut down even like that.

The flags to put on grub.config on yast: have we tried them all? Nohpet only worked for 4 days.

I don’t know where to hit my head anymore. Now new kernel 6.5.8 same story: won’t shut down.

karlmistelberger · October 24, 2023, 5:43am

ddtty:

After installing the propitiate NVIDIA driver, I found that each time doing
prime-select nvidia
after the re-login caused the system overheat and triggered the emergence power cut-off. And with propitiate NVIDIA driver installed, this laptop can not shutdown properly as the situation similar to the OP

Tumbleweed and Nvidia can be annoying: 60°C Idle Temperature on freshly installed Leap-15.4 KDE on a Lenovo Thinkpad W530 Notebook

Issue was bypassed by disabling the Nvidia GPU in UEFI. @christomonte11 now upgraded all ThinkPads to latest Tumbleweed. Maintenance follows procedures applied to infamous host erlangen.

Michele · October 24, 2023, 7:39am

It does not depend on Tumbleweed nor on Leap. I had the same problem on Fedora 38, Kubuntu and Xubuntu starting with the proprietary 535 driver. If I remember correctly with the 525 driver I had no problems.

Michele · October 24, 2023, 11:23am

I realized by giving the command
acpi -V
that I had not installed acpi.

sudo zypper in acpi

Now it shut down correctly, but I don’t know if it is just a fluke. I will do some testing during these days and tell you more.

ddtty · October 24, 2023, 1:10pm

But as I know that the acpi is just a tool to display some information related to your device. It is nothing to do with any configuration…

Michele · October 24, 2023, 7:14pm

You have right.

I’m turning off with

sudo shutdown -h now

It seems to be working fine. Ideally, I would like to add this shutdown command on ssdm. But there is sudo and it doesn’t work without a password.

karlmistelberger · October 25, 2023, 8:02am

Beware:

Michele · October 25, 2023, 8:34am

Hi Karl, I don’t recall reading anything dangerous about the administration of that command.
sudo shutdown now
is the classic shutdown command.

The addition of
-h or --halt takes care of safely disabling all connected devices as well.

I will tell you that many times I forget to unmount the external ssds. With -h I make myself safe.

karlmistelberger · October 25, 2023, 10:32am

Sure. However classic commands no longer exist and are emulated only. The canonical command is systemctl isolate ...:

erlangen:~ # systemctl isolate 
ctrl-alt-del.target         graphical.target            initrd.target               reboot.target
default.target              halt.target                 kexec.target                rescue.target
emergency.target            initrd-switch-root.service  multi-user.target           soft-reboot.target
exit.target                 initrd-switch-root.target   poweroff.target             system-update.target
erlangen:~ # systemctl isolate ^C
erlangen:~ #

You want to run systemctl isolate poweroff.target or the shorter poweroff

erlangen:~ # ll /sbin/poweroff 
lrwxrwxrwx 1 root root 16 Oct  9 11:11 /sbin/poweroff -> ../bin/systemctl
erlangen:~ #

You may want to check for plymouth and turn it off. Host thinkbook has it turned on:

thinkbook:~ # journalctl -b -1 -u 'plymouth*' --no-pager 
Oct 22 14:08:00 thinkbook systemd[1]: Starting Show Plymouth Boot Screen...
Oct 22 14:08:00 thinkbook plymouthd[497]: 00:00:01.579 ply-utils.c:932:ply_get_kernel_command_line                   : opening /proc/cmdline
Oct 22 14:08:00 thinkbook plymouthd[497]: 00:00:01.579 ply-utils.c:940:ply_get_kernel_command_line                   : reading kernel command line
Oct 22 14:08:00 thinkbook plymouthd[497]: 00:00:01.579 ply-utils.c:959:ply_get_kernel_command_line                   : Kernel command line is: 'BOOT_IMAGE=/boot/vmlinuz-6.5.6-1-default root=UUID=32e3b88f-b3c0-47cd-8cc3-d1ae89542954 splash=silent mitigations=auto quiet security=apparmor
Oct 22 14:08:00 thinkbook plymouthd[497]: '
Oct 22 14:08:00 thinkbook plymouthd[497]: 00:00:01.579 main.c:1938:check_logging                                     : checking if console messages should be redirected and logged
Oct 22 14:08:00 thinkbook plymouthd[497]: 00:00:01.579 main.c:1947:check_logging                                     : logging will be enabled!
Oct 22 14:08:00 thinkbook plymouthd[497]: 00:00:01.579 main.c:2017:initialize_environment                            : source built on Aug 28 2023
Oct 22 14:08:00 thinkbook systemd[1]: Started Show Plymouth Boot Screen.
Oct 22 14:08:03 thinkbook systemd[1]: Starting Plymouth switch root service...
Oct 22 14:08:03 thinkbook systemd[1]: Finished Plymouth switch root service.
Oct 22 14:08:05 thinkbook plymouthd[975]: 00:00:06.416 ply-utils.c:932:ply_get_kernel_command_line                   : opening /proc/cmdline
Oct 22 14:08:05 thinkbook plymouthd[975]: 00:00:06.417 ply-utils.c:940:ply_get_kernel_command_line                   : reading kernel command line
Oct 22 14:08:05 thinkbook plymouthd[975]: 00:00:06.417 ply-utils.c:959:ply_get_kernel_command_line                   : Kernel command line is: 'BOOT_IMAGE=/boot/vmlinuz-6.5.6-1-default root=UUID=32e3b88f-b3c0-47cd-8cc3-d1ae89542954 splash=silent mitigations=auto quiet security=apparmor
Oct 22 14:08:05 thinkbook plymouthd[975]: '
Oct 22 14:08:05 thinkbook plymouthd[975]: 00:00:06.417 main.c:1938:check_logging                                     : checking if console messages should be redirected and logged
Oct 22 14:08:05 thinkbook plymouthd[975]: 00:00:06.417 main.c:1947:check_logging                                     : logging will be enabled!
Oct 22 14:08:05 thinkbook plymouthd[975]: 00:00:06.417 main.c:2017:initialize_environment                            : source built on Aug 28 2023
Oct 22 14:08:05 thinkbook systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
Oct 22 14:08:05 thinkbook systemd[1]: plymouth-start.service: Found left-over process 497 (plymouthd) in control group while starting unit. Ignoring.
Oct 22 14:08:05 thinkbook systemd[1]: plymouth-start.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Oct 22 14:08:05 thinkbook systemd[1]: Starting Show Plymouth Boot Screen...
Oct 22 14:08:05 thinkbook systemd[1]: Finished Tell Plymouth To Write Out Runtime Data.
Oct 22 14:08:05 thinkbook systemd[1]: Started Show Plymouth Boot Screen.
Oct 22 14:08:07 thinkbook systemd[1]: Starting Hold until boot process finishes up...
Oct 22 14:08:07 thinkbook systemd[1]: Finished Hold until boot process finishes up.
Oct 22 21:51:26 thinkbook systemd[1]: plymouth-quit-wait.service: Deactivated successfully.
Oct 22 21:51:26 thinkbook systemd[1]: Stopped Hold until boot process finishes up.
Oct 22 21:51:26 thinkbook systemd[1]: Starting Show Plymouth Reboot Screen...
Oct 22 21:51:26 thinkbook plymouthd[5270]: 00:19:17.988 ply-utils.c:932:ply_get_kernel_command_line                   : opening /proc/cmdline
Oct 22 21:51:26 thinkbook plymouthd[5270]: 00:19:17.989 ply-utils.c:940:ply_get_kernel_command_line                   : reading kernel command line
Oct 22 21:51:26 thinkbook plymouthd[5270]: 00:19:17.989 ply-utils.c:959:ply_get_kernel_command_line                   : Kernel command line is: 'BOOT_IMAGE=/boot/vmlinuz-6.5.6-1-default root=UUID=32e3b88f-b3c0-47cd-8cc3-d1ae89542954 splash=silent mitigations=auto quiet security=apparmor
Oct 22 21:51:26 thinkbook plymouthd[5270]: '
Oct 22 21:51:26 thinkbook plymouthd[5270]: 00:19:17.989 main.c:1938:check_logging                                     : checking if console messages should be redirected and logged
Oct 22 21:51:26 thinkbook plymouthd[5270]: 00:19:17.989 main.c:1947:check_logging                                     : logging will be enabled!
Oct 22 21:51:26 thinkbook plymouthd[5270]: 00:19:17.989 main.c:2017:initialize_environment                            : source built on Aug 28 2023
Oct 22 21:51:26 thinkbook systemd[1]: Started Show Plymouth Reboot Screen.
Oct 22 21:51:26 thinkbook systemd[1]: Tell Plymouth To Jump To initramfs was skipped because no trigger condition checks were met.
thinkbook:~ #

Add plymouth.enable=0 to GRUB_CMDLINE_LINUX_DEFAULT:

erlangen:~ # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet loglevel=0 plymouth.enable=0 mitigations=off"
erlangen:~ #

Michele · October 25, 2023, 2:11pm

In the grub command line, I no longer enter any flags. In fact, I have tried to remove as many as possible. As for the:

systemctl isolate halt.target

thanks for the suggestion