Ubuntu
gnome-terminal package

gnome-terminal crashed with SIGSEGV in g_variant_unref()

Bug #816299 reported by Rohit Saraf on 2011-07-26

This bug report is a duplicate of: Bug #804946: gnome-settings-daemon crashed with SIGSEGV in g_variant_unref(). Edit Remove

This bug affects 18 people

Affects		Status	Importance	Assigned to	Milestone
	GNOME Terminal	New	Critical	gnome-bugs #655366
	gnome-terminal (Ubuntu)	Triaged	Medium	Unassigned

Bug Description

Seg Fault.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-terminal 3.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-6.7-generic 3.0.0-rc7
Uname: Linux 3.0.0-6-generic i686
Architecture: i386
CrashCounter: 1
Date: Tue Jul 26 14:08:16 2011
ExecutablePath: /usr/bin/gnome-terminal
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
ProcCmdline: gnome-terminal
ProcEnviron:
LANGUAGE=en_IN:en
LANG=en_IN
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x2b0213 <g_variant_unref+35>: lock xadd %eax,0x14(%esi)
PC (0x002b0213) ok
source "%eax" ok
destination "0x14(%esi)" (0x00000014) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
g_variant_unref () from /lib/i386-linux-gnu/libglib-2.0.so.0
g_settings_get () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
?? ()
?? ()
g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-terminal crashed with SIGSEGV in g_variant_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Rohit Saraf (rohit-kumar-saraf) wrote on 2011-07-26:

Dependencies.txt Edit (4.1 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (912 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (23.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (778 bytes, text/plain; charset="utf-8")
Registers.txt Edit (460 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (4.1 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (169.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-07-26:

StacktraceTop:
g_variant_unref (value=0x0) at /build/buildd/glib2.0-2.29.14/./glib/gvariant-core.c:617
g_settings_get (settings=0x8b47a00, key=0x807dc7f "monospace-font-name", format=0x8081d25 "&s") at /build/buildd/glib2.0-2.29.14/./gio/gsettings.c:1623
terminal_app_system_font_notify_cb (settings=0x8b47a00, key=0x807dc7f "monospace-font-name", app=0x8b44410) at terminal-app.c:977
terminal_app_init (app=0x8b44410) at terminal-app.c:1390
g_type_create_instance (type=3066048936) at /build/buildd/glib2.0-2.29.14/./gobject/gtype.c:1885

Revision history for this message

Apport retracing service (apport) wrote on 2011-07-26: Stacktrace.txt

Stacktrace.txt Edit (6.0 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2011-07-26: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (10.1 KiB, text/plain)

Changed in gnome-terminal (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Pedro Villavicencio (pedro) on 2011-07-26

visibility:

private → public

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2011-07-26:

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugzilla.gnome.org/show_bug.cgi?id=655366

Changed in gnome-terminal (Ubuntu):
status:	New → Triaged

Bug Watch Updater (bug-watch-updater) on 2011-07-26

Changed in gnome-terminal:
importance:	Unknown → Critical
status:	Unknown → New

Revision history for this message

Eliah Kagan (degeneracypressure) wrote on 2011-09-25:

I got this bug after an update that had not completed successfully, and the crash occurred every time I tried launching gnome-terminal. Then I ran "sudo apt-get -f install", and now I am able to launch gnome-terminal without problems. In the upstream bug (https://bugzilla.gnome.org/show_bug.cgi?id=655366), a developer has said that this seems specific to Ubuntu. Do other people who experience this bug have similar experiences?