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
Tested Hibernate in 17.10.
Playing Netflix in Google Chrome window, and browsing in another Google Chrome window.
Selected Hibernate from the topbar dropdown menu.
Hibernate worked fine, and computer restarted as expected.
Logged into Gnome-Shell as expected.
After loggin in, the desktop froze, and would not accept any mouse or keyboard input. (But audio continued to play).
After a minute, desktop became responsive.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Oct 22 23:06:17 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/
GsettingsChanges:
b'org.gnome.shell' b'command-history' b"['r']"
b'org.gnome.shell' b'app-picker-view' b'uint32 1'
b'org.gnome.shell' b'favorite-apps' b"['google-
b'org.
b'org.
InstallationDate: Installed on 2017-10-22 (1 days ago)
InstallationMedia: Ubuntu 17.10.0 2017.10.19 amd64 "Custom Artful Aardvark"
ProcCmdline: /usr/bin/
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f38ae0e7e0d <g_type_
PC (0x7f38ae0e7e0d) ok
source "0x16(%rax)" (0x100000016) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
g_type_
st_label_set_text () at /usr/lib/
g_object_setv () at /usr/lib/
g_object_
() at /usr/lib/
Title: gnome-shell crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy lpadmin plugdev sambashare sudo users video
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 #1722986, 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.