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
After a restart, and when Chrome was loading up, and asking for my Password. No big deal, as it did not even seem to crash - just the error. Perhaps it was related to the slow startup, which was oddly after rebooting into windows for a moment the rebooting back into Ubuntu. Both gave hiccups. And Ubuntu took an extra 10-20 seconds going to a black wallpaper and flashed a few times and did the NVidia "Dance" but figured it out. When X loaded it threw the error as stated above.
Just trying to help, Mark
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu5
ProcVersionSign
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 15 20:40:46 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2018-04-12 (3 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=en_CA:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_CA.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f964affcd3d <g_type_
PC (0x7f964affcd3d) ok
source "0x16(%rax)" (0x000093aa) not located in a known VMA region (needed readable region)!
destination "%edx" 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 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.