Screen freezes after waking from suspend with Gnome on Wayland

[Nicholas Stommel]

It appears that using Xorg instead of Wayland is the only way to fix this problem on Ubuntu 17.10. For some odd reason, whenever I wake my computer from suspend (especially after an extended period of time asleep) using Gnome in a Wayland session (gnome-session and stock ubuntu-session alike), my screen freezes completely on whatever was last there before suspending and I can't get any IO response at all. Nothing, the screen is totally frozen. I am also unable to exit into a recovery shell or kill GDM or gnome-session/ubuntu-session locally. I also can't seem to find any traces or indications for the freeze in the syslog, or maybe I'm just not sure where to look. I believe this is a problem with GDM on Wayland, not kernel related, as it happens on a totally stock install and when I use an upgraded/downgraded kernel. It literally necessitates restarting my computer. This problem is nonexistent when using Xorg instead of Wayland with GDM. Anyone else have this issue on Ubuntu 17.10 or figure out a solution better than simply switching to Xorg? I should clarify that I am not using nvidia drivers, I'm using Intel integrated graphics on a core-i7 5500U.

Ubuntu 17.10 uses gnome-session v3.26.1.
Expected behavior: When waking computer from suspend, expect GDM lock prompt and log back in.
What happened instead: When waking computer from suspend, screen and IO is completely frozen, necessitating a force-shutdown.

[Daniel van Vugt (vanvugt)]

Are you knowledgeable enough to log in remotely and attach a debugger to the gdm3 process when it is frozen? If so, please do and then paste the stack traces of the hung gdm3 process here.

But also...

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
  apport-collect 1728143
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Daniel van Vugt (vanvugt)]

If you're not sure how to use a debugger then you can download this script. Log in to the hung machine using ssh (needs openssh-server installed), and then run:

  sudo sh dstack gdm3 > traces.txt

And return traces.txt to us.

Alternatively run:

  sudo sh dstack gdm3

and just copy/paste the results into this bug.

[Nicholas Stommel (nstommel)]

Okay, I will try this with a fresh install of Ubuntu 17.10 and provide the necessary logs soon. I should be able to use the provided script over ssh, thanks. The problem with GDM freezing on Wayland after system resume/wakeup has been occurring ever since I ran the beta builds of 17.10, but it's clearly not fixed. I've been relatively busy lately, my apologies.

[Michael (mes2k)]

I am facing the exact same thing with a fresh install of 17.10 on my XPS 13 9343. The occurrence seems absolutely random, but it feels like the occurrence becomes more often over the time.

I will now switch to Xorg for both GDM and the session itself. I report back after some days.

For me, while the issue occurs I can still toggle the keyboard back light and the wireless kill switch. The network seems fully responsive, but as I logged in using SSH, I was not able to find any log messages or strange system behavior.

--
Greetings from 34c3 (just writing this in case anyone wants to meet for debugging :-))

[Daniel van Vugt (vanvugt)]

mes2k,

There are countless different possible causes for a bug like this, so please be sure to open a separate bug of your own.

[Launchpad Janitor (janitor)]

[Expired for gdm (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]