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
What caused this crash: using GNOME Universal Access setttings, I checked "high contrast" which succeeded, then unchecked "high contrast" which triggered a crash. When the GNOME shell restarted, it was still in high contrast mode. After the crash recovery, unchecking "high contrast" succeeded normally.
This has been a stable system until upgrading a day or two ago from Unbuntu 17.04 "zesty" to 17.10 "artful." I was not using Unity before or after the upgrade.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Tue Oct 24 12:20:16 2017
DisplayManager: lightdm
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2016-09-20 (399 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f16c8598e0d <g_type_
PC (0x7f16c8598e0d) ok
source "0x16(%rax)" (0x00021036) 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 () from /usr/lib/
g_object_setv () from /usr/lib/
g_object_
?? () from /usr/lib/
Title: gnome-shell crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to artful on 2017-10-23 (1 days ago)
UserGroups: adm audio cdrom dialout dip 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 #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.