gnome-shell crashed with signal 5 in _XIOError()

Bug #1704053 reported by Stephan Ruegamer on 2017-07-13
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Medium
Unassigned

Bug Description

After the last update this was starting to occure

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.10.0-26-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Wed Jul 12 09:04:20 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-05-16 (57 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-0.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: Upgraded to artful on 2017-06-14 (28 days ago)
UserGroups:

Stephan Ruegamer (sadig) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 _XIOError (dpy=dpy@entry=0x55b61359c800) at ../../src/XlibInt.c:1469
 _XEventsQueued (dpy=dpy@entry=0x55b61359c800, mode=mode@entry=2) at ../../src/xcb_io.c:352
 XPending (dpy=0x55b61359c800) at ../../src/Pending.c:55

Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Daniel van Vugt (vanvugt) wrote :

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.

information type: Private → Public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers