gnome-terminal crashed with SIGSEGV in g_type_check_is_value_type()

[Erik Johansson-Evegård]

Binary package hint: gnome-terminal

Crashed when switched of compiz.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-terminal 2.31.90-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
CrashCounter: 1
Date: Thu Aug 19 17:32:16 2010
ExecutablePath: /usr/bin/gnome-terminal
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: gnome-terminal
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc6e4b7bd0f <g_type_check_is_value_type+271>: cmpq $0x0,(%rax)
 PC (0x7fc6e4b7bd0f) ok
 source "$0x0" ok
 destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 g_type_check_is_value_type ()
 g_value_type_compatible ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: gnome-terminal crashed with SIGSEGV in g_type_check_is_value_type()
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

[Pedro Villavicencio (pedro)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Dennis Sheil (dennis-sheil)]

I have the same problem. When running gnome-appearance-properties (from the gnome-control-center package), in the visual effects tab I switch the visual effects state from normal to none. I guess my gnome-terminal is unable to handle this change.

I've installed the debug packages for gnome-terminal and for some of the involved libraries, and have attached a trace as requested. It is similar to the original trace for this report, but with the debug symbol packages my trace is more robust.

Not sure of everything as to how to reproduce, I have a bunch of windows open in my first workspace, I use an xterm to open the gnome-terminal session I'm debugging, then I clone (Open Terminal on the gnome-termnal) it three times and put a terminal in each workspace. At the top of workspace one and four are open terminals. In workspace four I open gnome-appearance-properties, make the switch, and segmentation fault happens in my gnome-terminal window. It does not seem to be able to handle this switch gracefully.

Trace with more debug symbols attached.

[Dennis Sheil (dennis-sheil)]

While looking through this, I realize there was another library that it would be good to have debug symbols for, libvte9, so I installed the debug symbols for that, reproduced the crash and attached the trace here.

The last trace within gnome-terminal before it goes off to the libraries is this one:

#9 0x000000000042460d in terminal_screen_realize (widget=0x9de0f0) at terminal-screen.c:301
        priv = 0x9ded60

If we look at the code after this line in terminal-screen.c we get -

   301 GTK_WIDGET_CLASS (terminal_screen_parent_class)->realize (widget);
   302
   303 /* FIXME: Don't enable this if we have a compmgr. */

The terminal_screen_realize function has six statements. Before the last two is this Fixme comment. So I guess that this has been a problem is already known, or at least, this has been a problem for something similar before.

[Dennis Sheil (dennis-sheil)]

Another thing I should mention - when in gnome-appearance-properties and switching the visual effects state from normal to none, if I have various windows of different programs in the different workspaces, they all wind up in the first workspace after the switch, as does my view. This seems to be more of a problem with the gnome-control-center package than gnome-terminal though. People should be able to turn off visual effects without being pulled to the first workspace, along with every other program.