gnome-shell crashed with signal 5
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Not sure is this is the crash on Wayland or on Xorg, but it happened on both.
When I logged back in, the screen was immediately locked and unlocking it would quickly result in the crash (reproduced the crash sequence about 3x, 2x on Wayland before I tried the Xorg session).
I have a bit of an interesting screen setup when in my docking-station that may be related:
One rotated screen (fullhd, HDMI), one "normal" screen (fullhd, DVI), and the laptop's main screen (highdpi, LVDS) turned off but the lid is open.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu1
ProcVersionSign
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Mon Oct 9 09:13:53 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
InstallationDate: Installed on 2017-05-30 (132 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
ProcCmdline: /usr/bin/
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
() at /usr/lib/
_XIOError () at /usr/lib/
_XReply () at /usr/lib/
XSync () at /usr/lib/
() at /usr/lib/
Title: gnome-shell crashed with signal 5
UpgradeStatus: Upgraded to artful on 2017-09-25 (13 days ago)
UserGroups:
| Andreas Brauchli (blk) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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.