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
......
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-terminal 3.24.2-0ubuntu4
ProcVersionSign
Uname: Linux 4.11.0-13-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Aug 6 14:34:57 2017
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2016-08-29 (342 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f628da99b61 <g_type_
PC (0x7f628da99b61) ok
source "$0x4" ok
destination "0x16(%rax)" (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-06-24 (43 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 #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.