I can't reboot or shut down the system in Leap 15.6

Hello. I am using a HP Envy Laptop Core Ultra 7 with Leap 15.6 Plasma KDE. I cannot reboot or shutdown the system, I have to press the keyboard button every time. I have reinstalled from scratch 3 times and the problem, sometimes absent at the beginning, with all updattes installled, appears sooner or later. First I thought that the problem were NVidia propietary drivers and I uninstalled them, but after a certain time it appeared again. I copy the output of inxi - b to see general data of the system:

inxi -b
System:
Host: localhost.localdomain Kernel: 6.4.0-150600.23.25-default arch: x86_64
bits: 64 Desktop: KDE Plasma v: 5.27.11 Distro: openSUSE Leap 15.6
Machine:
Type: Laptop System: HP product: HP Envy Laptop 17-da0xxx
v: Type1ProductConfigId serial:
Mobo: HP model: 8C68 v: 02.24 serial: UEFI: Insyde
v: F.02 date: 01/29/2024
Battery:
ID-1: BAT1 charge: 84.0 Wh (100.0%) condition: 84.0/83.0 Wh (101.2%)
CPU:
Info: 12-core (2-mt/10-st) Intel Core Ultra 7 155U [MST AMCP] speed (MHz):
avg: 400 min/max: 400/4700:3800:2100
Graphics:
Device-1: Intel Meteor Lake-P [Intel Graphics] driver: i915 v: kernel
Device-2: NVIDIA GA107M [GeForce RTX 3050 4GB Laptop GPU] driver: nvidia
v: 550.135
Device-3: Quanta HP 5MP Camera driver: hid-sensor-hub,usbhid,uvcvideo
type: USB
Display: x11 server: X.Org v: 1.21.1.11 with: Xwayland v: 24.1.1 driver:
X: loaded: modesetting,nvidia dri: iris gpu: i915 resolution: 1920x1080~60Hz
API: OpenGL v: 4.6.0 NVIDIA 550.135 renderer: NVIDIA GeForce RTX 3050 4GB
Laptop GPU/PCIe/SSE2
Network:
Device-1: Intel Meteor Lake PCH CNVi WiFi driver: iwlwifi
Drives:
Local Storage: total: 953.87 GiB used: 250.73 GiB (26.3%)
Info:
Processes: 394 Uptime: 0h 39m Memory: available: 30.97 GiB
used: 3.47 GiB (11.2%) Shell: Bash inxi: 3.3.27

Thank you in advance,

`

Aren’t there any messages during shutdown?
When you have the splash screen, then hit Esc to see them.

try ‘sudo reboot’, if it works the problem is plasma

Thank you. It is the same if I try to reboot from plasma or with sudo reboot. The system stops in a black background with de HP al Leap logos. If I press ESC nothing happens, I can’t see the messages.

Boot with plymouth.enable=0 and without quiet on the kernel command line. It may show more information.

Boot into runlevel 3 (append 3 to the kernel command line). Does the system shut down in this case?

Booting with plymouth.enable=0 no quiet shows information only at boot.
If I boot into runlevel 3 as root I cannot reboot or shut down (commands reboot, halt or init =0.

If you boot with plymouth disabled and without quiet - do you have any output at all when you run reboot or halt?

Yes, I have output, but I cannot understand it. Last 3 lines with halt refer to drm and nvidia (no compatible format)

Then you could at least post a photo.

Here is the photo.

@agbal

Nope - it also disables the splash screen at shutdown.

Just to be clear …
“halt” does not power down the machine - it merely stops the operating system without a power off.

So, you’re stating the command:

#  init 0

… does not power of the machine?
If yes, what is displayed after you execute “init 0” as root user?

Exactly the same as “halt”:

And what happens if you execute:

#  systemctl poweroff

It is the photo of the booted system waiting for someone to login. I do not see any reboot or halt command on this screen.

It is the final part of the messages that appear when I execute “sudo reboot” or halt or init 0

The same as with “halt” or “init 0”.

Try

systemctl -f poweroff

If this does not work

systemctl -ff poweroff

With systemctl -f poweroff the same as previous

With systemctl -ff poweroff :

sudo systemctl -ff poweroff

Powering off.

And stays here but it does not power off.

It looks like kernel issue. systemctl -ff poweroff just tells kernel to power off. You may try more recent kernel from Kernel:stable:Backport project. Does it work?

@agbal

I had this issue not long ago, and posted the response to someone who was also experiencing the “shutdown but does not power off”. Turns out it was a glitch with dracut. The OP of that thread changed to another kernel and that fixed it for them.

When was the last time you ran a “zypper up” ??? (your issue might be a bug).

My reply in that other thread: