gnome-terminal crashed with SIGSEGV in gtk_widget_style_get_valist()

Bug #630119 reported by Erik Johansson-Evegård
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-terminal (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnome-terminal

Crash occured when opening new terminal after switching off Compiz

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-terminal 2.31.90-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
NonfreeKernelModules: wl nvidia
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 4 12:33:27 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: 0x7f66840b3fed <gtk_widget_style_get_valist+221>: mov (%rax),%rdi
 PC (0x7f66840b3fed) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 gtk_widget_style_get_valist ()
 gtk_widget_style_get ()
 ?? () from /usr/lib/libvte.so.9
 ?? ()
 g_closure_invoke ()
Title: gnome-terminal crashed with SIGSEGV in gtk_widget_style_get_valist()
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

Revision history for this message
Erik Johansson-Evegård (erik-johansson-evegard) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 gtk_widget_style_get_valist ()
 gtk_widget_style_get ()
 vte_terminal_realize (widget=0x7f6674189780)
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.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
visibility: private → public
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.