Comment 0 for bug 1765269

Revision history for this message
alex (alexandersson) wrote : gnome-shell crashed with SIGSEGV

At upstart the problem occurred

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Wed Apr 18 19:50:57 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2018-04-08 (10 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7f01cd93a89b: mov 0x30(%rax),%edi
 PC (0x7f01cd93a89b) ok
 source "0x30(%rax)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
 meta_gpu_read_current () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
 meta_monitor_manager_read_current_state () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
 meta_monitor_manager_setup () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
 () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: