gnome-shell crashed with signal 5 in _XIOError()

[nvsoar]

Fault notice appeared before ubuntu update; submission rejected. Same fault notice appeared after daily ubuntu update at approximately 2045 14July2017, zone -7.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.2-0ubuntu7
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic i686
ApportVersion: 2.20.5-0ubuntu5
Architecture: i386
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Jul 14 20:36:20 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-07-13 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170426)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libmutter-0.so.0
 _XIOError () from /usr/lib/i386-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6
 XPending () from /usr/lib/i386-linux-gnu/libX11.so.6
 ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5 in _XIOError()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 x_io_error () from /tmp/apport_sandbox_t7SnHs/usr/lib/i386-linux-gnu/libmutter-0.so.0
 _XIOError (dpy=0x80d0c908) at ../../src/XlibInt.c:1469
 _XEventsQueued (dpy=0x80d0c908, mode=2) at ../../src/xcb_io.c:352
 XPending (dpy=0x80d0c908) at ../../src/Pending.c:55
 gdk_event_source_prepare () from /tmp/apport_sandbox_t7SnHs/usr/lib/i386-linux-gnu/libgdk-3.so.0

[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 1505409, 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.