gnome-shell crashed with SIGSEGV in g_closure_invoke()

[Benjamin Tegge]

Sorry I can't provide a detailed description nor can I find a recent duplicate. I got this prompt right after filing 3 new bug reports after upgrading to Artful.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu3
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Sep 9 02:19:07 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1504509861
GsettingsChanges:

InstallationDate: Installed on 2016-03-01 (557 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /var/lib/gdm3
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7f11b01af836: mov 0x1a0(%rax),%rax
 PC (0x7f11b01af836) ok
 source "0x1a0(%rax)" (0x000001a0) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
 meta_monitor_manager_kms_wait_for_flip () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to artful on 2017-09-09 (0 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 #1714330, 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.