gnome-terminal-server crashed with SIGSEGV in gdk_display_get_event()

[Heath Malmstrom]

Gnome locked up while attempting to edit settings of the Dash to Dock Gnome Extension. X windows respawned (I am running in xorg gnome as the stock one doesn't work with my second monitor -- at login it just respawns back to the login when I choose that).

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-terminal 3.24.2-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 18 22:43:57 2017
ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
InstallationDate: Installed on 2015-10-23 (726 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
SegvAnalysis:
 Segfault happened at: 0x7f566c173dd8: mov 0x90(%r14),%rsi
 PC (0x7f566c173dd8) ok
 source "0x90(%r14)" (0x00000090) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-terminal-server crashed with SIGSEGV in gdk_display_get_event()
UpgradeStatus: Upgraded to artful on 2017-10-11 (8 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

[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 #1664613, 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.