GNOME Terminal

gnome-terminal crashed with SIGABRT in g_assertion_message()

Bug #944382 reported by Pierre-Olivier Megret on 2012-03-01

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	GNOME Terminal	Won't Fix	Critical	gnome-bugs #582234
	gnome-terminal (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Crash occurs after a Unity general freeze when I tried to scan my music collection with banshee.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-terminal 3.3.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.93-0ubuntu2
Architecture: amd64
Date: Thu Mar 1 22:45:52 2012
ExecutablePath: /usr/bin/gnome-terminal
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
ProcCmdline: gnome-terminal
ProcEnviron:
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-terminal
StacktraceTop:
raise () from /lib/x86_64-linux-gnu/libc.so.6
abort () from /lib/x86_64-linux-gnu/libc.so.6
g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
Title: gnome-terminal crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Tags:

Revision history for this message

Pierre-Olivier Megret (sorrodje) wrote on 2012-03-01:

Dependencies.txt Edit (4.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (854 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (42.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (818 bytes, text/plain; charset="utf-8")
Registers.txt Edit (695 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.3 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (5.0 KiB, text/plain; charset="utf-8")

security vulnerability:

no → yes

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-01:

StacktraceTop:
g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x438e10 "terminal_app_handle_options", message=0x1e6c2f0 "assertion failed: (profile)") at /build/buildd/glib2.0-2.31.18/./glib/gtestutils.c:1860
g_assertion_message_expr (domain=0x0, file=0x4385ba "terminal-app.c", line=1817, func=0x438e10 "terminal_app_handle_options", expr=<optimized out>) at /build/buildd/glib2.0-2.31.18/./glib/gtestutils.c:1871
terminal_app_handle_options (app=0x1cc9030, options=0x1b82000, allow_resume=1, error=0x7fff1b63b038) at terminal-app.c:1817
name_acquired_cb (connection=<optimized out>, name=<optimized out>, user_data=0x1b80cb0) at terminal.c:275
do_call (client=0x1b83c30, call_type=CALL_TYPE_NAME_ACQUIRED) at /build/buildd/glib2.0-2.31.18/./gio/gdbusnameowning.c:215

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-01: Stacktrace.txt

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

Revision history for this message

Apport retracing service (apport) wrote on 2012-03-01: ThreadStacktrace.txt

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

Changed in gnome-terminal (Ubuntu):
importance:	Undecided → Medium
summary:	- gnome-terminal crashed with SIGABRT in raise() + gnome-terminal crashed with SIGABRT in g_assertion_message()
tags:	removed: need-amd64-retrace

Tyler Hicks (tyhicks) on 2012-03-02

security vulnerability:	yes → no
security vulnerability:	yes → no
visibility:	private → public
visibility:	private → public

Revision history for this message

Vadim Rutkovsky (roignac) wrote on 2012-03-05:

Found upstream bug - https://bugzilla.gnome.org/show_bug.cgi?id=582234

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

Bug Watch Updater (bug-watch-updater) on 2012-03-12

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

Bug Watch Updater (bug-watch-updater) on 2018-11-09

Changed in gnome-terminal:
status:	New → Won't Fix

Revision history for this message

Paul White (paulw2u) wrote on 2018-12-27:

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

Do you still see a problem related to the one that you reported in a currently supported version of Ubuntu? Please let us know if you do and in which version otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]