gnome-shell crashed with signal 5 in _XIOError()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10
Ubuntu's error reporting system didn't give me much to go on, but I'm guessing gnome-shell crashed sometime this past week, I rebooted into Cinnamon, and Ubuntu's tool is just now giving me the opportunity to report it (as it told me one or more files was missing the last time I tried to report it, but an apt update/upgrade has resolved that). I didn't see any bugs that matched exactly on a simple check. A Google search led to multiple bugs w/ the same error message that are mostly duplicates of:
https:/
though one was a dupe of:
https:/
I'm running the Dev branch, so I expect bugs. Just posting to help in case it's not a duplicate. Wish there were a better way to tell if this was a dupe so as to not waste your time if it is.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.2-0ubuntu7
Uname: Linux 4.12.0-
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat Jul 15 20:06:46 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
InstallationDate: Installed on 2017-02-20 (146 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcCmdline: /usr/bin/
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
?? () from /usr/lib/
_XIOError () from /usr/lib/
_XReply () from /usr/lib/
XSync () from /usr/lib/
?? () from /usr/lib/
Title: gnome-shell crashed with signal 5 in _XIOError()
UpgradeStatus: Upgraded to artful on 2017-05-08 (68 days ago)
UserGroups:
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 #1556601, 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.