gnome-terminal crashed with SIGSEGV in g_type_check_instance_is_a()

Bug #1302461 reported by sunsik
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-terminal (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

 -

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-terminal 3.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
Uname: Linux 3.13.0-22-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Apr 4 18:55:52 2014
ExecutablePath: /usr/bin/gnome-terminal
InstallationDate: Installed on 2013-08-14 (232 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcCmdline: gnome-terminal
SegvAnalysis:
 Segfault happened at: 0x7f582accad6c <g_type_check_instance_is_a+60>: testb $0x4,0x16(%r8)
 PC (0x7f582accad6c) ok
 source "$0x4" ok
 destination "0x16(%r8)" (0x400000016) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 gtk_widget_get_parent () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-terminal crashed with SIGSEGV in g_type_check_instance_is_a()
UpgradeStatus: Upgraded to trusty on 2014-03-19 (16 days ago)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
sunsik (sunsik) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_is_a (type_instance=0x1e02e20, iface_type=<optimized out>) at /build/buildd/glib2.0-2.40.0/./gobject/gtype.c:3969
 gtk_widget_get_double_buffered (widget=<optimized out>) at /build/buildd/gtk+3.0-3.10.7/./gtk/gtkwidget.c:8715
 ?? ()
 sync_tab_label (screen=<optimized out>, pspec=<optimized out>, label=0x1e02e20) at terminal-tab-label.c:74
 g_closure_invoke (closure=0x1f0ca70, return_value=0x0, n_param_values=2, param_values=0x7fffff348300, invocation_hint=0x7fffff3482a0) at /build/buildd/glib2.0-2.40.0/./gobject/gclosure.c:768

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-terminal (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Seth Arnold (seth-arnold) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-terminal (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.