gnome-shell crashed with signal 5 immediately upon booting to Unity desktop

Bug #1725422 reported by Jonathan Goble on 2017-10-20
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Undecided
Unassigned

Bug Description

After upgrading from Zesty to Artful and playing around in the GNOME desktop briefly, I decided to go back to Unity after upgrading the kernel (I use the TuxOnIce kernels for hibernation support, and do not have the stock kernels installed at all). Upon booting into Unity on the new kernel, this error popped up almost immediately. I don't understand the error well enough to have any clue what's going on.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19~ppa1-generic-tuxonice 4.13.4
Uname: Linux 4.10.0-37-generic-tuxonice x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Oct 20 14:21:57 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-04-19 (183 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: gnome-shell crashed with signal 5
UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
UserGroups:

Jonathan Goble (jcgoble3) wrote :

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers