gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()

Bug #729458 reported by Vadim Peretokin on 2011-03-05
This bug affects 11 people
Affects Status Importance Assigned to Milestone
gnome-terminal (Ubuntu)

Bug Description

Binary package hint: gnome-terminal

Crashed out of the blue.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-terminal 2.32.1-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Mar 4 20:44:39 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-terminal
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcCmdline: gnome-terminal
 Segfault happened at: 0x7fc4bb961cfd <g_type_check_instance_cast+61>: mov (%rsi),%r13
 PC (0x7fc4bb961cfd) ok
 source "(%rsi)" (0x0000001d) not located in a known VMA region (needed readable region)!
 destination "%r13" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-terminal
 g_type_check_instance_cast () from /usr/lib/
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 g_main_context_dispatch () from /lib/
 ?? () from /lib/
Title: gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Vadim Peretokin (vperetokin) wrote :

 g_type_check_instance_cast (type_instance=0xa2c2d0, iface_type=9403136) at /build/buildd/glib2.0-2.28.1/./gobject/gtype.c:3990
 bus_got_cb (obj=<value optimized out>, result=<value optimized out>, user_data=0xa2c2d0) at /build/buildd/libdbusmenu-0.3.100/./libdbusmenu-glib/server.c:704
 complete_in_idle_cb (data=<value optimized out>) at /build/buildd/glib2.0-2.28.1/./gio/gsimpleasyncresult.c:757
 g_main_dispatch (context=0x82fa40) at /build/buildd/glib2.0-2.28.1/./glib/gmain.c:2440
 g_main_context_dispatch (context=0x82fa40) at /build/buildd/glib2.0-2.28.1/./glib/gmain.c:3013

Changed in gnome-terminal (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Oneiric Ocelot. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at . Thanks again and we appreciate your help.

Changed in gnome-terminal (Ubuntu):
status: New → Incomplete
Daniel Hahler (blueyed) wrote :

"Crashed out of the blue" Is not reproducible.
Marking Confirmed according to duplicate.

Changed in gnome-terminal (Ubuntu):
status: Incomplete → Confirmed
visibility: private → public
Guilherme Salgado (salgado) wrote :

In my case it seems to have crashed while running an 'apt-get upgrade'. That was the only terminal window I had but it was not in focus so it's possible the upgrade had finished when it crashed. (bug 956432 has the trace)

Tamas Papp (tompos) wrote :

The same heere with Precise, I was typing something remotely through ssh on a server.

Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.

Do you still see a problem related to the one that you reported in a currently supported version of Ubuntu? Please let us know if you do and in which version otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]

Changed in gnome-terminal (Ubuntu):
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for gnome-terminal (Ubuntu) because there has been no activity for 60 days.]

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

Duplicates of this bug

Other bug subscribers