Ubuntu
terminator package

terminator crashed with SIGSEGV in gtk_entry_get_display_mode()

Bug #976158 reported by Max Bowsher on 2012-04-07

52

This bug affects 9 people

Affects		Status	Importance	Assigned to	Milestone
	terminator (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

Terminator crashed; I think I'd pressed Ctrl+Shift+I (create new window) at the time, though this doesn't reproduce the crash.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: terminator 0.96-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
Date: Sat Apr 7 20:07:02 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/share/terminator/terminator
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/terminator
ProcEnviron:
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: terminator
Title: terminator crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: Upgraded to precise on 2012-03-31 (7 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sbuild

Tags:

Revision history for this message

Max Bowsher (maxb) wrote on 2012-04-07:

#1

Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (572 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (73.1 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (824 bytes, text/plain; charset="utf-8")
Registers.txt Edit (745 bytes, text/plain; charset="utf-8")
SegvAnalysis.txt Edit (198 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (2.0 KiB, text/plain; charset="utf-8")
StacktraceTop.txt Edit (321 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (4.6 KiB, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2012-04-07: Stacktrace.txt

#3

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

Revision history for this message

Apport retracing service (apport) wrote on 2012-04-07: StacktraceTop.txt

#4

StacktraceTop.txt Edit (666 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2012-04-07: ThreadStacktrace.txt

#5

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

Changed in terminator (Ubuntu):
importance:	Undecided → Medium
summary:	- terminator crashed with SIGSEGV in g_signal_emit_valist() + terminator crashed with SIGSEGV in gtk_entry_get_display_mode()
tags:	removed: need-amd64-retrace

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-09-26:

#6

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in terminator (Ubuntu):
status:	New → Confirmed

Revision history for this message

TraceyC (grrlgeek) wrote on 2015-08-20:

#7

I just found this bug when apport on Linux Mint reported the same crash as the original title of this bug report
"terminator crashed with SIGSEGV in g_signal_emit_valist()"

Unfortunately it looks like apport decided to discard / ignore the crash reporting when I said that yes, this is the bug that affects me.

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #1550339

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.