gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()

Bug #189656 reported by Nic
146
This bug affects 7 people
Affects Status Importance Assigned to Milestone
GNOME Terminal
Expired
Critical
gnome-terminal (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-terminal

I had just changed the number of scrolling lines in the current profiles from 500 to 1300. When I hit "close" the terminal crashed. I can' t reproduce it unfortunately.

ProblemType: Crash
Architecture: i386
Date: Wed Feb 6 17:56:27 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-terminal
NonfreeKernelModules: nvidia
Package: gnome-terminal 2.21.90-0ubuntu1
PackageArchitecture: i386
ProcCmdline: gnome-terminal
ProcCwd: /home/nt271
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=C
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
 g_type_check_instance_cast ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()
Uname: Linux constantines 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Tags: apport-crash
Revision history for this message
Nic (ntetreau) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:terminal_screen_reread_profile (screen=0x8101ae0) at terminal-screen.c:619
IA__g_cclosure_marshal_VOID__POINTER (closure=0x874dd10, return_value=0x0,
IA__g_closure_invoke (closure=0x874dd10, return_value=0x0, n_param_values=2,
signal_emit_unlocked_R (node=0x80dd678, detail=0, instance=0x80df710, emission_return=0x0,
IA__g_signal_emit_valist (instance=0x0, signal_id=129, detail=0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in gnome-terminal:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=514830

Changed in gnome-terminal:
assignee: nobody → desktop-bugs
status: New → Triaged
Changed in gnome-terminal:
status: Unknown → New
Revision history for this message
Michael B. Trausch (mtrausch) wrote :

Would like to comment that I have encountered this bug myself, same crash, different trigger. In my case, I triggered the bug by going to Edit→Current Profile…→Colors, and unchecking the box that says "Use colors from system scheme". The good news is that it managed to save the intended settings to gconf anyway and it wasn't a horrible situation, though I did have child processes running in the terminal at the time. Oh, well. :)

Hopefully this one is squashed soon.

Revision history for this message
Michael B. Trausch (mtrausch) wrote :

I just encountered bug 188344 in Brasero, and it looks like that these two bugs are related and that there are several dupes of each.

Is this a bug with GLib, or is this a bug in the client applications which use GLib? Any idea of a way to find out that information?

Revision history for this message
Mike Basinger (mike.basinger) wrote :

Just happened to me when switching font for gnome-terminal

Revision history for this message
Pepijn van de Geer (pvandegeer) wrote :

Happened to me when switching font size.

Revision history for this message
Horst der Biber (sexyhorst69) wrote :

Happened to me when switching background for gnome-terminal.

Revision history for this message
wozzinator (cwoz36) wrote :

I have my default profile set up to be transparent so I can see my background and anything underneath the terminal and it crashed while I was lowering the transparency. I can get it to crash every single time for some reason.

Revision history for this message
Chris J Arges (arges) wrote :

I had 3 terminals open, in one I was scp'ing a large file. I decided to change the default font, and I unchecked the box, and then gnome-terminal crashed. I can't reproduce this bug, now I can check/un-check the default font box fine.

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

Thanks, there's no need to add more comments for now, the bug has been sent upstream in case they ask for more info we'll ask you to submit it, thanks!.

Revision history for this message
Reece (reece) wrote :

Happened to me after changing a terminal "custom command".

Revision history for this message
SVWander (windycitybythebay) wrote : Re: [Bug 189656] Re: gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()

were you able to get the fonts back? Right now it is impossible for me to enter commands because the screen is blank. It was suggested that I edit /boot/grub/menu.lst The suggestion was I was to get rid of the word "quiet splash" It didn't help so I am still without a command line on that machine. At least in X.
Tim

----- Original Message ----

From: Reece <email address hidden>
To: <email address hidden>
Sent: Sunday, April 6, 2008 12:06:59 PM
Subject: [Bug 189656] Re: gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()

Happened to me after changing a terminal "custom command".

--
gnome-terminal crashed with SIGSEGV in g_type_check_instance_cast()
https://bugs.launchpad.net/bugs/189656
You received this bug notification because you are a direct subscriber
of a duplicate bug.

      ____________________________________________________________________________________
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
http://tc.deals.yahoo.com/tc/blockbuster/text5.com

Revision history for this message
nstriedinger (nathan00) wrote :

crashed when changing fore-ground color in gconf-editor.

Revision history for this message
ridcully (mail-engel-stefan) wrote :

Crashed when disabling terminal bell on 'General' tab. Clicking on 'Close' and other tabs did nothing and I could move the window around for some time (5-10 secs) before the edit dialog crashed. The change had been saved.

Revision history for this message
Cinar Sahin (csahin) wrote :

Crashed when I did the following:

Edit --> Current Profile --> Scrolling --> [changed the kilobytes entry and hit enter]

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

fixed on trunk, thanks.

Changed in gnome-terminal:
status: Triaged → Fix Committed
Changed in gnome-terminal:
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

the new version is available in ubuntu now

Changed in gnome-terminal:
status: Fix Committed → Fix Released
Revision history for this message
Rob (robklg) wrote :

Good to see it's fixed..
I was just about to report it, because now i'm able to reproduce this.

This bug happens when you have multiple gnome-terminal's opened. And *if* you close one *window* (and not exit the shell), and afterwards you change a profile setting... then the crash happens.

Hope this is fix is in ubuntu soon..

Changed in gnome-terminal:
importance: Unknown → Critical
status: Invalid → Expired
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.