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
This crash isn't something that is reproducible and is the first I have seen for some time.
I woke my laptop from suspend mode and used Firefox for about twenty minutes. I tried to open LibreOffice Calc and my system froze completely. No response from keyboard. After a minute or so GNOME Shell restarted and I could again use my laptop. Shortly after I was prompted to report the issue.
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSign
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.10-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat May 26 08:41:10 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-11-07 (199 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fb6f8049d12 <g_type_
PC (0x7fb6f8049d12) ok
source "(%rdi)" (0x00000001) 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: Upgraded to cosmic on 2018-02-21 (93 days ago)
UserGroups: adm cdrom dip kvm lpadmin 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 #1759621, 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.