Comment 0 for bug 1783673

Revision history for this message
Zhenqing Hu (huzq85) wrote : gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()

NA

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.28.3-0ubuntu2
ProcVersionSignature: Ubuntu 4.17.0-4.5-generic 4.17.3
Uname: Linux 4.17.0-4-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.10-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Wed Jul 25 21:54:39 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2018-06-18 (37 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7f3325479e50: mov 0x128(%rdi),%rax
 PC (0x7f3325479e50) ok
 source "0x128(%rdi)" (0x00000128) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
 clutter_x11_handle_event () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: