gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This is a more detailed report for a previously reported bug (#1723882) occurring with Ubuntu 17.10 in a dual screen setup. Crashes appear to be linked to notifications appearing. Initially they would just result in the session crashing and going back to the login screen, but in the meantime I had a few occasions where the shell would just lock up and not allow any further interaction.
However, this might have been lack of patience on my part, since this time it did go back to the login screen after while and left behind the .crash file used for this bug report.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu3
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 10:01:14 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-07-03 (105 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: /usr/bin/
SegvAnalysis:
Segfault happened at: 0x7f66b85aecdf <g_type_
PC (0x7f66b85aecdf) ok
source "(%rdx)" (0x1e8126810e26
destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
g_type_
g_value_set_object () from /usr/lib/
g_object_
?? () from /usr/lib/
?? () from /usr/lib/
Title: gnome-shell crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to artful on 2017-10-09 (7 days ago)
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 #1723705, 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.