gnome-terminal crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

Bug #327801 reported by Lars Düsing
14
Affects Status Importance Assigned to Milestone
gnome-terminal (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-terminal

Adding a new character-coding.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-terminal
Package: gnome-terminal 2.25.5-0ubuntu2
ProcCmdline: gnome-terminal
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: gnome-terminal crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Uname: Linux 2.6.28-7-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Lars Düsing (lars.duesing) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #205536. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

is this reproducible ? may you tell us a few easy steps in order to trigger the issue? thanks in advance.

Changed in gnome-terminal:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Daniel Holbach (dholbach) wrote :

Can you try again with 2.25.91-0ubuntu2?

Revision history for this message
Lars Düsing (lars.duesing) wrote :

Pedro, Sorry, I cannot reproduce the bug.
I've tried it many times. Something very weird happend...

Revision history for this message
Lars Düsing (lars.duesing) wrote :

I can reproduce the bug now.
It happens if you add a new encoding to gnome-terminal via Menu "Terminal"->"Encoding"->"Add new encoding" (or such, localized version here...)
Problem is solved with current gnome-terminal.

Revision history for this message
Lars Düsing (lars.duesing) wrote :

Problem doesnt happen any more with current gnome-terminal

Changed in gnome-terminal:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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