gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-terminal (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crashed few seconds after opening. It was inactive that time. I've just updated from 17.4. Dell XPS13 3960
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-terminal 3.24.2-0ubuntu4
ProcVersionSign
Uname: Linux 4.13.0-
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 23:07:26 2017
DistributionCha
# This is a distribution channel descriptor
# For more information see http://
canonical-
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2016-11-18 (335 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f94dedac77e <g_type_
PC (0x7f94dedac77e) ok
source "$0x4" ok
destination "0x16(%rdx)" (0x70000001e) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
g_type_
gtk_widget_
() at /usr/lib/
gtk_window_
gtk_window_
Title: gnome-terminal-
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
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 #1438014, 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.