gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Please prioritize fixing this issue. It happens almost every time I resume from suspend, regardless of running Xorg or Wayland.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSign
Uname: Linux 4.13.0-30-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sat Feb 3 21:15:07 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-12-09 (56 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7fa3d9c17de2 <g_type_
PC (0x7fa3d9c17de2) ok
source "(%rdi)" (0x00000086) not located in a known VMA region (needed readable region)!
destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
g_type_
st_label_set_text () at /usr/lib/
ffi_call_unix64 () at /usr/lib/
ffi_call () at /usr/lib/
() at /usr/lib/
Title: gnome-shell crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
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 #1714989, 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.