gnome-shell crashed with signal 5 in _XIOError()

[ROCHE]

Sorry, always the same bug ! But as I don't speak english so good, I can't understand what is saying in bugs report.
Do you want I make some test on my computer to help you?
My pc .... always the same..
GL753V core I7 7700
 I don't know what that this bug... All function work well !

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Sep 30 15:27:30 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-02-16 (231 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-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:
 wayland_selection_update_x11_property (data=0x556853f42010) at wayland/meta-xwayland-selection.c:671
 _XIOError (dpy=dpy@entry=0x556853f42010) at ../../src/XlibInt.c:1469
 _XEventsQueued (dpy=dpy@entry=0x556853f42010, mode=mode@entry=2) at ../../src/xcb_io.c:352
 XPending (dpy=0x556853f42010) at ../../src/Pending.c:55
 _gdk_x11_window_move_resize_child (window=0x556853c5ac40, x=1, y=-617366168, width=0, height=-617366160) at ././gdk/x11/gdkgeometry-x11.c:52

[Daniel van Vugt (vanvugt)]

Seems the stack trace has changed but this is still essentially bug 1505409