gnome-shell crashed with signal 5 in _XIOError()

[Jamie Sterling]

Ubuntu Mate 17.10

I was having a problem with my Focaltech touchpad on my Asus laptop - the right click didn't work.

https://bugs.launchpad.net/bugs/1725210

Title:
  Focaltech touchpad right click doesn't work

Alexander Browne from the bug team said "AFAIK 17.10 is the first release to use the libinput touchpad driver by
default and drop the synaptics driver, but synaptics stills works if you
install it (or upgrade from an install that had it like my current
system). So try installing synaptics

    sudo apt install xserver-xorg-input-synaptics

and reboot."

I did this and I got this new bug.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Oct 21 10:31:20 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
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)]

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