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
Computer freezes for about 5 minutes (mouse only can move, but no input from keyboard nor mouse are recorded).
Logs filled with tons of :
org.gnome.
gnome-shell[1837]: g_object_set: assertion 'G_IS_OBJECT (object)' failed
gnome-shell[1837]: g_object_set: assertion 'G_IS_OBJECT (object)' failed
gnome-shell[1837]: clutter_
gnome-shell[1837]: g_object_set: assertion 'G_IS_OBJECT (object)' failed
gnome-shell[1837]: g_object_set: assertion 'G_IS_OBJECT (object)' failed
gnome-shell[1837]: clutter_
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu2
ProcVersionSign
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Wed Oct 4 20:23:23 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-01-15 (262 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f2f14e5ce56 <g_type_
PC (0x7f2f14e5ce56) ok
source "(%rdi)" (0x00c0104b) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
g_type_
() at /usr/lib/
g_closure_invoke () at /usr/lib/
() at /usr/lib/
g_signal_
Title: gnome-shell crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to artful on 2017-10-03 (1 days ago)
UserGroups: adm cdrom dip disk lpadmin plugdev sambashare sudo vboxusers wireshark
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 #1714745, 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.