Issue to suspend my computer

Ask Fedora
1

Hello,

I am having a problem with the suspend mode on my Fedora computer. When I try to put my computer into sleep mode, nothing happens.

Here the output of the logs :

Mar 28 23:27:35 fedora gnome-shell[3126]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack >
                                          @resource:///org/gnome/gjs/modules/core/overrides/Gio.js:193:20
                                          suspend@resource:///org/gnome/shell/misc/loginManager.js:199:21
                                          activateSuspend@resource:///org/gnome/shell/misc/systemActions.js:474:28
                                          _init/<@resource:///org/gnome/shell/ui/status/system.js:184:33
                                          addAction/<@resource:///org/gnome/shell/ui/popupMenu.js:758:21
                                          activate@resource:///org/gnome/shell/ui/popupMenu.js:193:14
                                          _init/<@resource:///org/gnome/shell/ui/popupMenu.js:110:24
                                          @resource:///org/gnome/shell/ui/init.js:21:20
Mar 28 23:27:40 fedora systemd[2922]: Started app-gnome-ptyxis-90557.scope - Application launched by gsd-media-keys.
Mar 28 23:27:41 fedora ptyxis[90557]: MESA-INTEL: warning: Haswell Vulkan support is incomplete
Mar 28 23:27:41 fedora ptyxis[90557]: MESA-INTEL: warning: ../src/intel/vulkan_hasvk/anv_formats.c:790: FINISHME: support more multi-planar formats with DRM modifiers
Mar 28 23:27:41 fedora ptyxis[90557]: MESA-INTEL: warning: ../src/intel/vulkan_hasvk/anv_formats.c:759: FINISHME: support YUV colorspace with DRM format modifiers
Mar 28 23:27:41 fedora systemd[2922]: Started ptyxis-spawn-ce371acf-dcb8-4dca-9d74-31212aeae525.scope - [systemd-run] /usr/bin/bash.
Mar 28 23:27:43 fedora gnome-software[32612]: 23:27:43.406 › [useAuthWebsocket] document is not visible, will defer reconnection when document becomes visible.
Mar 28 23:27:54 fedora gnome-software[32612]: 23:27:54.406 › [useAuthWebsocket] [20282466ms] heartbeat timeout, reconnecting.
Mar 28 23:27:54 fedora gnome-software[32612]: 23:27:54.406 › [useAuthWebsocket] Could not complete Remote Auth login, trying to restart with a new Remote Auth session.
Mar 28 23:28:24 fedora gnome-software[32612]: 23:28:24.409 › [useAuthWebsocket] document is not visible, will defer reconnection when document becomes visible.
Mar 28 23:28:35 fedora gnome-software[32612]: 23:28:35.405 › [useAuthWebsocket] [20323466ms] heartbeat timeout, reconnecting.
Mar 28 23:28:35 fedora gnome-software[32612]: 23:28:35.405 › [useAuthWebsocket] Could not complete Remote Auth login, trying to restart with a new Remote Auth session.

Thanks all in advance for all tips you can give me to fix this issue.

Best regards.

3

This a really common issue that normally is the result of hardware manufacturers not updating the linux kernel to match their hardware.
It’s a know issue, for something like 10 years, and I don’t have a fix for you.

For the sake of posterity, can you upload a inxi -Fzxx and then when and if someone works on it, they can see your hardware and kernel versions.

4

As mentioned:

Power management requires cooperation between the UEFI/BIOS firmware and the linux kernel. At one time Linux often needed vendor-specific code to work around BIOS problems, but that is unworkable as new hardware appears almost every day. Hardware vendors and Linux have developed standards for power management and legacy vendor-specific code is being removed or in some cases, inadvertently broken with newer kernels. These issues often first appear in Fedora, but will affect other distros as they moved to newer kernels. In cases where the hardware vendor fails to fix an issues, a Linux user affected by the issue may provide a detailed bug report and workaround or fix. Linux depends heavily on this sort of community support, so users who encounter power management problems need to find ways to share details. As mentioned, including the inxi -Fzxx report as web-searchable text will allow others with similar hardware and issues find this topic.

You can also provide a (very detailed) probe using https://linux-hardware.org and check other probes for the same hardware. Note that this site is often overwhelmed so may take several attempts to get a connection.

Since your issue probably affects multiple Linux distros, a search of forums for other distros may find a workaround or even a prper solution.

1 Like
5

or it’s not available

cat /sys/power/mem_sleep

or maybe it’s blocked

systemd-inhibit --list
gnome-session-inhibit --list

@watramer , what happens when you issue the command systemctl suspend?