gnome-shell crashed with signal 5 in _XReply()

[Koos]

Gnome shell crashed after a close of gnome terminal with a hanging connection to a remote side.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 9 10:58:11 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2017-04-03 (189 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/bin/gnome-shell
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XIGetClientPointer () from /usr/lib/x86_64-linux-gnu/libXi.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to artful on 2017-08-31 (38 days ago)
UserGroups: adm libvirt lpadmin sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 XIGetClientPointer (dpy=0x5618ff73a430, win=win@entry=0, deviceid=deviceid@entry=0x7ffed1f46944) at ../../src/XGetCPtr.c:59
 gdk_x11_display_get_default_seat (display=0x5618ff747080) at ././gdk/x11/gdkdisplay-x11.c:2889
 get_pointer_position_gdk (mods=0x0, y=0x7ffed1f469b4, x=0x7ffed1f469b0) at backends/meta-cursor-tracker.c:374
 meta_cursor_tracker_get_pointer (tracker=tracker@entry=0x5618ff4c5f20, x=x@entry=0x7ffed1f469b0, y=y@entry=0x7ffed1f469b4, mods=mods@entry=0x0) at backends/meta-cursor-tracker.c:419
 meta_screen_get_mouse_window (screen=0x5618ff65a5c0, not_this_one=not_this_one@entry=0x0) at core/screen.c:1504

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1701289, so it 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. Feel free to continue to report any other bugs you may find.