Laptop freezes following closing and opening the lid

I recently purchased a Slimbook Pro 15 X.
It’s an AMD Ryzen 7 5000 series CPU, Radeon graphics.

I asked that the laptop ship with Slimbook OS (a variation of Ubuntu) just so that it had a linux install on their when it arrived. I wanted to see what “goodies” Slimbook shipped the machine with on top of the standard OS.

There were a couple things, like an AMD GPU tool, battery tool, face login etc… but not enough for me to stay on there.

I wiped the machine.

Wiped = I ran `sudo efibootmgr -Bb 0001" (for each entry in the efibootmgr) so that all the boot loaders were gone for Slimbook OS. I say bootloader… I mean the list of entries that tend to build up when I’ve distro hopped in the past and I end up with a boot option for every distro I’ve ever installed on a device.

After that, I installed a distro (take your pick, I’ve probably tried it at this point) with LVM and full disk encryption, and without, and combinations.

No matter what distro, what combination of encryption and disk layout, which desktop environment… closing the lid and opening it again causes a system failure (in different ways, depending on the distro).

It’s resulted in a black screen with nothing, a login screen I can’t interact with at all, a login screen that let’s me enter my password but doesn’t login, it does log in but then nothing on the desktop opens (with errors about read only filesystem)

I’ve looked into this type of issue on various forums - I’ve seen recommendations of adding acpiphp.disable=1 to the grub config but that’s not resolved it on any distro I’ve tried.

I’ve moved on to FEdora 37 to see if the latest and greatest from Fedora’s new release would resolve the issue but still nothing. So I’ve decided to stick with a distro and ask members of that community for help.

Happy to provide any logs etc that are requested. It’s not possible to check without restarting the machine following the lid close and open.

Hi Jake, I have the same problem with an AMD Ryzen™ 7 5700U with Radeon™ Let me know if you found a solution :slight_smile:

I am continuing investigate this topic …

I figured out that a smart
[root@tuxi julius]# echo mem > /sys/power/state

works without any problems …


in Ubuntu 22.04 I can’t reproduce this bug

After a fresh install it worked for some days fine,
but some day later the bug returns. Is there anybody out there who has an idea where/what to look for?

My workaround is:
as root →

alias standby='loginctl lock-session && echo mem > /sys/power/state'

it works fine, but it is not realy elegant