Hybrid-sleep not working any more

English Install/Boot/Login
1

In one of my machines hybrid-sleep has stopped working. It used to work there, too. Now it just reports an error:

# systemctl hybrid-sleep 
Call to HybridSleep failed: Sleep verb "hybrid-sleep" not supported

I compared configuration to another machine, where hybrid-sleep works. I came up with nothing. Also, googling error message did not give any help. I don’t know where to look as keyword “hybrid-sleep” containing target file, service file, sleep.conf, binaries and libraries are identical in those machines.

2

difference in hardware???

3

Machine where hybrid-sleep used to work has had the very same hardware all the time.

4

same hardware then check that all you need is installed on both

5

Could you please specify what to check? I have no clue where to look.

Both machine – the one where hybrid-sleep is not curretly workin, and the other where hybrid-sleep works – has up-to-date patched OpenSuse Tumbleweed.

6

I don’t use TW and hybrid-sleep does not show in my repos.

So open yast software and check requires and provides boxes and search see where it comes from and what needs it.

7

Hybrid-sleep is part of systemd functionality. So it cannot be installed separately.

8

well something provides it and something may require it

9

If you don’t even know what systemd is and what it does, please shut up.

10

I know what it is do you?? just trying to point out trouble shooting possibilities since you say the hardware is identical the difference has to be software or configuration.

Well I’m done. So far no one else has jumped in .

11

@jiivee I suggest you review the openSUSE Forum Terms and Conditions and refrain from this type of rhetoric against other Forum users!

Are both machines running the same Tumbleweed snapshot cat /etc/os-release are both systems using secure boot mokutil --sb-state and booting this way, are both systems running the same kernel?

If secure boot is in use, then you may need to disable, else check the /etc/systemd/logind.conf settings are all the same.

2 Likes
12

Both machines have the same TW snapshot 20231226 and kernel 6.6.7.

The machine, which has has working hybrid-sleep, has secure boot disabled (*.
The machine, where hybrid-sleep fails, has secure boot enabled.

/usr/lib/systemd/logind.conf is the same default file in both machines, i.e. all settings are commented out. /etc/systemd/logind.conf does not exist in either machine. Directories /usr/lib/systemd/logind.conf.d/ and /etc/systemd/logind.conf.d/ are empty in both machines.

I checked also a laptop for systemctl hyprid sleep (has same TW snapshot as above) and has secure boot enabled. There hybrid-sleep fails with same message as in the opening post of this thread. However, systemctl suspend works in all these machines. I’ve been using hybrid-sleep mainly because it more reliably let wol packets wake up machines.

So, is this hybrid-sleep case somehow related to how secure boot works and is Managed in OpenSuse TW nowadays?

(* Secure boot has worked in this machine earlier and I have not intentionally turned it off. I remember seeing there the blue MOK screen many times.

13

Which explains why hibernation does not work.