Can't come back from suspend

General system Newbie
1

Hello. I’m having a weird issue with Suspend on Gnome 41.2 after installing yesterday from the most recent ISO: I am greeted with a black screen after I suspend the session and the only way I can return is to power cycle the computer (it’s a desktop, not a laptop).

Some attempts to fix it:

  • Simplest one: powercycling the monitor, because my monitor had some weird interactions with sleep in the past. Doesn’t work.

  • Changed to the LTS kernel (I’m using the 5.15 by default), but the problem persists there. This was according to the suggestion given by one of the posts here with a similar issue.

  • Changed to a Wayland session, as I am in X11 by default (I have a Nvidia gpu). Actually what happens here is that I can see parts of the UI instead of a blackscreen so I can log back but to a broken, almost entirely black desktop, which makes me believe this is a graphics issue.

  • According to the other topic here with a similar issue, enabling

sudo systemctl enable nvidia-suspend.service
sudo systemctl enable nvidia-hibernate.service
sudo systemctl enable nvidia-resume.service

fixed for him, but that didn’t work for me. In fact, no matter what I do, the services remain inactive (dead) for me.

Running journalctl --since "10 minutes ago" didn’t provide any information that was useful for me.

As said before, I am using the 5.15 kernel by default, and the 495.96 proprietary Nvidia driver. What is even weirder is that I was using exactly this if I remember correctly with my KDE install until friday with absolutely no issue.

EDIT: Forgot to say, I didn’t make any changes to gnome-shell or display manager (using gdm).

2 Likes
2

Don’t enable these services - they are not intended to be used by anything other than systemd’s suspend target. Wait, let me check the thread I read. It might have been “don’t start those services”. Ah yes, it was “don’t start them”, https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150/15

I’m seeing the same issue - there’s a regression somewhere along the line. The two main elements that have been updated recently are the kernel and the Nvidia driver, so downgrading one then the other will likely identify which is at fault.

3

So, this is weird:

I did a clean reinstall, booted up on the LTS kernel (5.10) and then installed the nvidia 470 drivers, and not the 495 that I had installed before through dkms, and I still have the problem which makes no sense to me honestly. Next step is probably just install KDE and hope this is somehow a Gnome issue.

1 Like
4

Right - this is a “known issue” with Wayland sessions at the moment. This also points it towards being related to X rather than anything else.

[2021-12-15T16:33:53+0000] [ALPM] upgraded xorg-server-common (21.1.1-3 -> 21.1.2-1)
[2021-12-15T16:33:53+0000] [ALPM] upgraded xorg-server (21.1.1-3 -> 21.1.2-1)

Can you check your update timestamps and see whether this package update ties in to the time window when you found the issue started?

5

I checked and I have both on

xorg-server-21.1.2-1

xorg-server-common  21.1.2-1

The band-aid “fix” for me was just switching for lightdm.

1 Like
6

Seems to be confirmed it’s an Xorg issue here:

with a fix coming:

Edit: Confirm, seems to fix things for me. Anyone following along can grab the package(s) from my repo: xorg-server (sig).

4 Likes
7

In testing, will be in stable soon:

3 Likes
8

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.