gnome-shell crashed with signal 5 after restart

Bug #1759869 reported by ricsdeol on 2018-03-29
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Undecided
Unassigned

Bug Description

Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Upgrade from 17.10

gnome-shell:
  Installed: 3.28.0-0ubuntu1
  Candidate: 3.28.0-0ubuntu1
  Version table:
 *** 3.28.0-0ubuntu1 500
        500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

xorg:
  Installed: 1:7.7+19ubuntu5
  Candidate: 1:7.7+19ubuntu5
  Version table:
 *** 1:7.7+19ubuntu5 500
        500 http://br.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

The error occurred after login, but no visible side effects were displayed, only the appearance of ubuntu report error.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Thu Mar 29 11:11:48 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-10-23 (156 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libmutter-2.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 bionic on 2018-03-26 (2 days ago)
UserGroups:

ricsdeol (ricardo.s.o.leite) 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 #1748450, 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