Regardless of the way suspend is triggered, it does not work. Reproducible: Always Steps to Reproduce: 1a. Click on the suspend button from the GNOME menu, or… 1b. …Close the lid 2. The screen goes black but the device stays on. Actual Results: The device does not go into suspension mode. The screen goes black but actually everything else stays on. Expected Results: The device should properly go into suspension. Related thread on Fedora Discussion forum: https://discussion.fedoraproject.org/t/suspend-not-working/81465 Is there a way to troubleshoot/debug this issue? I really do not know how to provide more information.
I have a similar problem with my HP Pavilion x360 (14-dy0183TU). However, it's not specific to GNOME, and it only happens when I close the lid. Suspend and Hibernate both work fine when assigned to the power button instead. Can you share additional details about your laptop model? Also, are you able to reproduce it without a desktop environment?
I have the same issue on KDE, so most likely it's not related to desktop environments. It seems to me that this problem happens when I have resource-heavy apps/processes open/running, but I'm not sure about that. I can reproduce this issue both when closing the lid and pressing the suspend button. Linux congard-fedora 6.2.15-200.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 15:56:33 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Strix G513
The extension is shown as not compatible with GNOME 44 on Fedora 38.
OP selected the wrong component, this is likely a PM issue and it has nothing to do with GNOME or any DE in particular. It's reproducible on many distros for affected devices (e.g. HP 14-dy0183TU 11th Gen), as I mentioned earlier). In my case, I've successfully reproduced this bug on: - Debian 12 - Ubuntu 23.04 - Fedora 38 - openSUSE Tumbleweed - Arch Linux (both with and without a desktop environment) I've been trying to debug this for months without any luck. Related: https://github.com/systemd/systemd/issues/27665
Agree, looks so. However, my comment on the extension not working is valid. So hopefully that can be resolved.
Even after disabling all the GNOME extensions I have installed, and after upgrading to Linux kernel `6.3.8-200.fc38.x86_64`, for me **the problem persists**!
To avoid confusion, I created https://bugzilla.redhat.com/show_bug.cgi?id=2219768 to report the extension itself to incompatible with GNOME 44.