I am running Tumbleweed with Gnome.
Recently, I have seen an issue where the monitor is not turning on after resuming from a suspended state.
The monitor uses a Display Port connection.
I can start another Session by pressing Ctrl + Alt + Fx, then the monitor will turn on, and I can switch back to my old Session.
I have started observing this issue since last week
I have tried updating my Tumbleweed to the latest.
But, unfortunately, I can still see it happening.
I think I am seeing this issue if any Applications installed via Flatpak are running during Suspend (but I am not 100% sure about this).
Is anyone else facing a similar issue?
I would appreciate your helpful responses
I did have the same problem on other distro (Ubuntu, Debian 12.2 and fedora 39 with gnome, and of course on suse!) as well! So it’s not a Suse problem!
I do have dual monitor setup (6k and 4k display from Dell)
I have read it could be the kernel problem or something else!
I do have Sapphire RX 7900XTX OC
Thanks! for the reply Sjostrand. I have a single monitor setup and don’t have a dedicated Graphics card. But, since you have this issue in other distros running Gnome as well; then I think I better do some research and see if this issue is already reported in the Gnome bug tracker.
I had a problem from the previous nvidia 535.129.02 .run installer and the newest new feature branch version 545.29.06.
The new production branch version 535.129.03 solve this problem.
My experience here was the monitor turns on but no gui. The monitor is on with black screen but with the mouse cursor that I can move anywhere. I can also go back to gui with Ctrl-Alt-Backspace. This doesn’t happens all the time, it only happens when I suspend for a few hours.
I use the suspend function very often but now have the same problem. I started having these problems a couple of weeks ago. If I understand correctly, it has to do with NVIDIA drivers not playing well with kernel 6.6. Since then NVIDIA has been updated once, suspend worked exactly once, then returned to its faulty behaviour. May be it is a matter of waiting for another update(s).