I was also hit by this issue on a `HP ProBook 635 Aero G7 (2E9E4EA)` with a `AMD Ryzen 7 4700U with Radeon Graphics`.
I found (by experiments) a different solution: Calling (as root) `/lib/systemd/systemd-sleep suspend` makes the wake up from suspend to work every time (not only the first time). This has the drawback that the screen is not locked. Then I did the following (with a passwordless sudo rule for `/lib/systemd/systemd-sleep`): ~~~ /usr/bin/xdg-screensaver lock; sudo /lib/systemd/systemd-sleep suspend ~~~ In this configuration, I had back the old buggy behaviour (2nd suspend does not wake up). I switched now to ~~~ sudo /lib/systemd/systemd-sleep suspend; /usr/bin/xdg-screensaver lock ~~~ and this works reliably. Unfortunately, there is a short moment where the plain screen content is visible after wake up, but the screen is locked almost immediately. So this is hacky, but **far more** better than before, as I can now use suspend and hibernate :-) * If the laptop is stolen suspended, the attacker has less than half a second to see what is on the screen, then it is locked * If the laptop is stolen hibernated, the attacker needs the disk encryption password before the machine really boots. Maybe this weird setup helps in debugging. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2008774 Title: Ubuntu 22.04 not waking up after second suspend Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After the first suspend it wakes up just fine - it's the second suspend after which the screen stays blank and keyboard doesn't react (although the power LED starts glowing). It happens if I close the laptop's lid or do a manual suspend via the system menu. It happens only recently (I think after some kernel update, but I'm not sure about this) - before it worked fine for month (since I installed Ubuntu). I have a recent Thinkpad T14s with a Ryzen CPU, Ubuntu 22.04 is the only OS (if that's important). What I tried: * turn off security chip in the BIOS (https://askubuntu.com/a/1412049/424896) * turn off Wayland and enable X11 (https://askubuntu.com/a/1412032/424896) * I looked through the logs in /var/log but couldn't find anything obvious to me (but I'm not a Linux guru). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-32-generic 5.19.0-32.33~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 28 11:02:36 2023 InstallationDate: Installed on 2022-06-14 (258 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2008774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
