gnome-shell crashed with SIGSEGV

[Rocko]

This happens every time I turn off the primary (and only) monitor on my Intel NUC, which is attached to the HDMI port. If I turn the monitor back on straight away, I get a blank screen for some time (maybe 20-30 seconds) and then the GDM login screen appears. All unsaved data in the previous gnome-shell is lost.

The crash has been happening ever since around mid-August last year in Ubuntu 17.10, and is still happening in Bionic.

This bug looks similar to bug #1714886 but apparently that is already fixed in this version of gnome-shell (3.26.2-0ubuntu2).

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
Uname: Linux 4.13.0-22-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 11 10:45:41 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2017-02-27 (317 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170225)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f2c69d4f1bc: mov 0x18(%rax),%esi
 PC (0x7f2c69d4f1bc) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 meta_window_x11_configure_request () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: Upgraded to bionic on 2017-12-21 (20 days ago)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1726352, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.