On 02/07/2021 06.46, Felix Miata wrote:
This PC is my brother's, originally installed 24 months ago by myself with 15.1. He claims sleep/hibernate used to work before the upgrade to 15.2, and now 15.3. He wants hibernate/sleep to work again. So far, I haven't found the secret to success.
...
To generate the following, I first booted to multi-user, logged in as root, then issued systemctl start systemd-suspend. The response was no different that I could tell than by selecting sleep or hibernate from Plasma's Power/Session menu.
The command is "systemctl hibernate". I have no idea if the one you use is equivalent or not.
Contains no information on "hibernate".
# journalctl -b https://paste.opensuse.org/10906426
Contains no hibernation attempt. The only thing I see is that the kernel checks to see if there is an hibernation image stored, and fails, there is no such image. Jul 01 23:11:23 rok68 systemd[1]: Starting Resume from hibernation using device /dev/disk/by-label/P02swapper... Jul 01 23:11:23 rok68 systemd-hibernate-resume[337]: Could not resume from '/dev/disk/by-label/P02swapper' (8:2). Jul 01 23:11:23 rok68 kernel: PM: Image not found (code -22) Jul 01 23:11:23 rok68 systemd[1]: systemd-hibernate-resume@dev-disk-by\x2dlabel-P02swapper.service: Succeeded. Jul 01 23:11:23 rok68 systemd[1]: Finished Resume from hibernation using device /dev/disk/by-label/P02swapper. Jul 01 23:11:23 rok68 systemd[1]: Reached target Local File Systems (Pre).
My search fu is fubar again. I was sure there was recent discussion about this subject either on a mailing list or on the forums, but I'm not finding it.
Is there anything in the two logs to explain why an attempt to suspend or hibernate results either in:
1-several seconds of black screen without a poweroff, then all coming back as if resume had been intentionally triggered, or 2-several seconds of black screen without a poweroff, then all coming back as if screenlocker had been triggered, or 3-reboot
There is no hint that such a thing ever happened. Start the machine in level 3, then login as root and issue "systemctl hibernate". If it fails, extract the logs just at that instant. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)