gnome-terminal crashed with SIGSEGV in gtk_style_attach()

[Abhinav Modi]

Binary package hint: gnome-terminal

gnome-terminal crashed, without any specific user interaction. Was trying to find which of multiple terminals to switch to, using compiz hotkeys (ring switcher)

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-terminal 2.31.90-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-17.23-generic 2.6.35.2
Uname: Linux 2.6.35-17-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
CheckboxSubmission: be713317570882f6fea9a8be9c9248c0
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Fri Aug 27 17:53:21 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-terminal
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: gnome-terminal
ProcEnviron:
 LANG=en_IN
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb679b311d6 <gtk_style_attach+38>: cmp %r13,(%rax)
 PC (0x7fb679b311d6) ok
 source "%r13" ok
 destination "(%rax)" (0x0000000b) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 gtk_style_attach ()
 ?? () from /usr/lib/libvte.so.9
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: gnome-terminal crashed with SIGSEGV in gtk_style_attach()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

[Apport retracing service (apport)]

StacktraceTop:
 gtk_style_attach ()
 ?? ()
 ?? ()
 vte_terminal_realize (widget=0x9adc00)
 terminal_screen_realize (widget=0xac3ad0)

[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.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.