gnome-shell crashed with signal 5 in _XIOError() from _XReply() from XRRGetMonitors()

Bug #1562587 reported by Jose Gómez
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

nouveau crashed when I unplugged my HDMI monitor (will report that bug separately). On startup, I have seen this error.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-shell 3.18.4-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Mar 27 20:56:21 2016
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2014-02-04 (782 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140203)
ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/libmutter.so.0
 _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XRRGetMonitors () from /usr/lib/x86_64-linux-gnu/libXrandr.so.2
 ?? () 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:

Revision history for this message
Jose Gómez (adler-dreamcoder) wrote :
Revision history for this message
Jose Gómez (adler-dreamcoder) wrote :

Actually, it may not have been nouveau what crashed (I just thought that because once I unplugged the external HDMI monitor I only saw a black screen with a nouveau message).

But actually, that message seems to be old, produced during startup.

Some of the logs may give a hint of what crashed when the HDMI cable was unplugged.

Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 x_io_error () from /tmp/apport_sandbox_sCuyae/usr/lib/libmutter.so.0
 _XIOError (dpy=dpy@entry=0x24ae000) at ../../src/XlibInt.c:1464
 _XReply (dpy=dpy@entry=0x24ae000, rep=rep@entry=0x7ffe8e547d00, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:708
 XRRGetMonitors (dpy=0x24ae000, window=608, get_active=get_active@entry=1, nmonitors=nmonitors@entry=0x7ffe8e547dbc) at ../../src/XrrMonitor.c:61
 init_randr15 (screen=0x24c41f0) at /build/gtk+3.0-a73mKw/gtk+3.0-3.18.9/./gdk/x11/gdkscreen-x11.c:640

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: gnome-shell crashed with signal 5 in _XIOError()

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
information type: Private → Public
tags: added: xorg
summary: - gnome-shell crashed with signal 5 in _XIOError()
+ gnome-shell crashed with signal 5 in _XIOError() from _XReply() from
+ XRRGetMonitors()
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 16.04 (xenial) reached end-of-life on April, 2019

https://ubuntugnome.org/ubuntu-gnome-16-04-lts-is-here/
https://wiki.ubuntu.com/XenialXerus/ReleaseNotes/UbuntuGNOME

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.