gnome-terminal crashed with SIGSEGV in g_object_notify()

Bug #860330 reported by Joni Kurunsaari
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gnome-terminal (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I was installing KVM with command "sudo apt-get install qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils". I did have 2 tabs open, another running htop and another window running sshclient. Hardware Macbook Pro 7.1

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-terminal 3.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Tue Sep 27 10:45:49 2011
ExecutablePath: /usr/bin/gnome-terminal
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110921.2)
ProcCmdline: gnome-terminal
SegvAnalysis:
 Segfault happened at: 0x7f31deff82f8 <g_object_notify+56>: cmpq $0x50,(%rax)
 PC (0x7f31deff82f8) ok
 source "$0x50" ok
 destination "(%rax)" (0x00000001) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 g_object_notify () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.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
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-terminal crashed with SIGSEGV in g_object_notify()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Joni Kurunsaari (joni-kurunsaari-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_object_notify (object=<optimized out>, property_name=0x7f31e0243382 "accessible-value") at /build/buildd/glib2.0-2.29.92/./gobject/gobject.c:1003
 g_closure_invoke (closure=0x1e30020, return_value=0x0, n_param_values=1, param_values=0x1feac80, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.29.92/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=0x1e05370, emission_return=0x0, instance_and_params=0x1feac80) at /build/buildd/glib2.0-2.29.92/./gobject/gsignal.c:3272
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=0x7fff77244878) at /build/buildd/glib2.0-2.29.92/./gobject/gsignal.c:3003
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.29.92/./gobject/gsignal.c:3060

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
Jeremy Bícha (jbicha)
visibility: private → 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
tags: added: raring
Revision history for this message
Bryan Quigley (bryanquigley) wrote :

Does this issue happen for anyone repeatedly? If so, could you describe what you are doing at the time.

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.