Waking from suspend doesn't work with Nvidia Gnome

[pradaker]

Describe the bug

I had been using Bazzite with KDE Plasma for a few months without issue. Yesterday, I decided to reinstall Bazzite but this time with Gnome, and most things have been fine. However, I am now not able to wake my PC from sleep. When I try, my display powers on for a brief moment, and then shuts off. The PC still has power, but it's not connected to the network, my keyboard/mouse doesn't seem to do anything, and even the power button does nothing unless I hold it down to forcefully shut it off.

System logs: https://www.dropbox.com/scl/fi/v1s87xgg1hwid8ky3yoo3/85e837b0.txt

System info: https://www.dropbox.com/scl/fi/cw05uxdrbi5ckl4ui0tqz/9f1ff574.txt

UPDATE: I disabled AMD IOMMU in my BIOS, but that didn't fix it. After reading through system logs, the issue seems to be something running in the gnome shell that doesn't want to suspend, but I haven't managed to find what exactly the culprit is.

UPDATE 2: I fixed it! My issue seemed to be that gnome-shell was trying to interact with the Nvidia driver after it already went into a suspended state, so the solution is to suspend gnome-shell beforehand so it doesn't try to do that.

I followed the guide on the second post in this thread made by "gabekings":
https://bbs.archlinux.org/viewtopic.php?id=277713

I hope this helps someone!

What did you expect to happen?

I expected the system to wake up and resume

Output of rpm-ostree status

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome-nvidia-open:stable
                   Digest: sha256:e8fdf9440b2231b75939652c21c3134a43f05135cbe4a547d1f2a5423ca01913
                  Version: 41.20250325 (2025-03-25T20:32:46Z)
          LayeredPackages: openrazer-daemon

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:9459dfc02f5d3c4bb9aba135333002e7021cb364e435fa51eacdca52e41ff72e
                  Version: 41.20250325 (2025-03-25T20:29:21Z)
          LayeredPackages: openrazer-daemon

Hardware

Mobo: Asus ROG STRIX B650E-F Gaming WiFi
CPU: AMD Ryzen 9 7900X
GPU: Nvidia GeForce RTX 4090
RAM: 32GB

Extra information or context

I didn't change any hardware during the switch from KDE Plasma to Gnome

[tduarte]

Installed Bazzite last night and I'm having the same issue.

[SanelessOne]

I wonder if you're having the same issue as me

#2429

[natesevn]

FWIW, I have the same issue with bazzite-gnome-nvidia-open. I've also encountered the same with the KDE version bazzite-nvidia-open. It sounds like there was an issue with the MT7922 Wifi card module that was fixed as of Linux 6.12.8, but I'm still seeing it on Linux 6.13.7.

[tduarte]

@natesevn I’m running an Intel WiFi card, it looks like the only common denominator is the NVIDIA gpu.

[natesevn]

I was browsing through more user issues and came across this one which perfectly describes what I'm seeing: #1904

Interestingly enough, it repros on AMD GPUs too.

[HopeSilent]

Can also confirm this issue is present for me on bazzite gnome with nvidia closed. It's running on a Ryzen 5 5600T in a Asrock B450m Pro4 with a GTX 1070. No ability to resume from suspend (no video output), have to hold the power button to force it off and then freshly boot up. This post by Radioactive_Doomer on Reddit appears to discuss a similar issue that was resolved by doing the following:

"In case anyone else has this issue I fixed it. It was combination of AMD IOMMU making the gfx card inaccessible and some pci device controller triggering wake up.

I set amd_iommu=off in the GRUB command line options and used /proc/acpi/wakeup to find the offending device and disable wake signals."

This is the only reference I've found to the issue, indicating it was something to do with IOMMU, which I've already verified is disabled in my BIOS.

[Colcobau]

Having the exact same issue on my machine for the last couple of weeks. This only started recently, and was not an issue before.

Turning off IOMMU is not really an option for me.

[kumail-r]

@Colcobau I see you might have missed the solution linked in the issue by OP, I just tried it and it worked for me (similar background, this problem started a few weeks ago on my system with an RTX 3090 + Ryzen 7000 CPU).

Instructions:

1. Create /usr/local/bin/suspend-gnome-shell.sh and put this script in it:

#!/bin/bash

case "$1" in
    suspend)
        killall -STOP gnome-shell
        ;;
    resume)
        killall -CONT gnome-shell
        ;;
esac

2. Make the script executable (thanks @Imasu):

sudo chmod +x /usr/local/bin/suspend-gnome-shell.sh

3. Do the same for /etc/systemd/system/gnome-shell-suspend.service:

[Unit]
Description=Suspend gnome-shell
Before=systemd-suspend.service
Before=systemd-hibernate.service
Before=nvidia-suspend.service
Before=nvidia-hibernate.service

[Service]
Type=oneshot
ExecStart=/usr/local/bin/suspend-gnome-shell.sh suspend

[Install]
WantedBy=systemd-suspend.service
WantedBy=systemd-hibernate.service

4. Do the same for /etc/systemd/system/gnome-shell-resume.service:

[Unit]
Description=Resume gnome-shell
After=systemd-suspend.service
After=systemd-hibernate.service
After=nvidia-resume.service

[Service]
Type=oneshot
ExecStart=/usr/local/bin/suspend-gnome-shell.sh resume

[Install]
WantedBy=systemd-suspend.service
WantedBy=systemd-hibernate.service

6. Finally, run these commands:

systemctl daemon-reload
systemctl enable gnome-shell-suspend
systemctl enable gnome-shell-resume

[Colcobau]

@kumail-r Oh, I didn't miss it, and I can do that no problem, it's just that the whole point of atomic desktops is NOT having to do these things. But I guess as a workaround I might give it a go.

Edit: Now realising I might've come off rude, do apologise, had a long day. I do appreciate you going out of your way to paste the workaround on the reply.

[Colcobau]

Worth noting, I tried the suggested fix and the issue persists.

[HopeSilent]

I can also confirm that the steps noted by @kumail-r did not resolve the issue for me.

[fpatrick]

I am also having the this problem for 2 weeks (rtx 3060 ti). I thought it was related to a new nvidia driver, if gnome have such a big issue for weeks I would say nvidia's gpu owners should never use it. unfortunately.

[Imasu]

I confirm that the steps noted by @kumail-r resolved the issue for me, provided to make the shell executable :
sudo chmod +x /usr/local/bin/suspend-gnome-shell.sh

[HopeSilent]

I confirm that the steps noted by @kumail-r resolved the issue for me, provided to make the shell executable : sudo chmod +x /usr/local/bin/suspend-gnome-shell.sh

Thank you, @Imasu, I definitely face-palmed reading that. Script works as intended with appropriate privileges. I also see dramatic improvement in the amount of time it takes to go to sleep as it, presumably, is no longer fighting to do so.

Hopefully this won't be necessary in the future?