gnome-terminal crashed with SIGSEGV (detaching tabs)

Bug #187358 reported by JP Foster
28
Affects Status Importance Assigned to Milestone
GNOME Terminal
Fix Released
High
gnome-terminal (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-terminal

I detached a tab when I only had one tab. This created one window with one tab and one window with no tabs.
I then used the menu to detach a tab from the window with no tabs.
This causes all gnome-terminals to crash.
I know this is kind of a pathological thing to do, but I was surprised that all the terminals died.
If there is no open terminal in a window dethach tab should be greyed out probably

ProblemType: Crash
Architecture: i386
Date: Wed Jan 30 17:28:00 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-terminal
NonfreeKernelModules: nvidia
Package: gnome-terminal 2.21.5-0ubuntu1
PackageArchitecture: i386
ProcCmdline: gnome-terminal
ProcCwd: /home/jpfoster
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
Signal: 11
SourcePackage: gnome-terminal
Stacktrace: #0 0x08068e37 in ?? ()
StacktraceTop: ?? ()
ThreadStacktrace:

Title: gnome-terminal crashed with SIGSEGV
Uname: Linux jp-pc 2.6.24-5-386 #1 Thu Jan 24 19:04:50 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev sambashare scanner video

Tags: apport-crash
Revision history for this message
JP Foster (jeepster) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:

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. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-terminal:
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
JP Foster (jeepster) wrote :

Backtrace didn't work here is the output of it. Looks from the stack trace that the first thing to fix is to check system->priv is valid before dereferencing it. (from stacktrace source.txt)

GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/gnome-terminal
[Thread debugging using libthread_db enabled]
[New Thread 0xb6d6e6b0 (LWP 25035)]

Program exited normally.
(gdb) backtrace full
No stack.
(gdb) info registers
The program has no registers now.
(gdb) thread apply all backtrace
No registers.
(gdb) quit

Revision history for this message
Elio Bezerra da Silva (elio7769-deactivatedaccount-deactivatedaccount) wrote : Re: [Bug 187358] Re: gnome-terminal crashed with SIGSEGV (detaching tabs)

Parem de me mandar email, já estão enchendo o saco!!!

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

there's no backtrace there, closing this report for now, thanks.

Changed in gnome-terminal:
status: Incomplete → Invalid
Revision history for this message
Tim Lesher (tlesher) wrote :

Happens reproduceably for me on Hardy Beta x86_64; reopening and attaching backtrace.

JP Foster: the reason the backtrace didn't appear to work is that by default, gnome-terminal will exit if another terminal process is already running. So the process your debugger created detected your open terminal process, switched to it, and exited. To prevent this, run it from the debugger with the --disable-factory.

Changed in gnome-terminal:
status: Invalid → New
Revision history for this message
Tim Lesher (tlesher) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

thanks, may you install the following packages: libglib2.0-0-dbgsym, libgtk2.0-0-dbgsym and get a new trace? thanks in advance.

Changed in gnome-terminal:
status: New → Incomplete
Revision history for this message
Tim Lesher (tlesher) wrote :

Attached.

Changed in gnome-terminal:
status: Incomplete → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

thanks you will forward upstream.

Changed in gnome-terminal:
status: New → Confirmed
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=524366

Changed in gnome-terminal:
status: Confirmed → Triaged
Revision history for this message
ubunturox (ubunturox-kk) wrote :

i have the same experience.

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

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

fixed on gnome-terminal trunk, thanks you.

Changed in gnome-terminal:
status: Triaged → Fix Committed
Changed in gnome-terminal:
status: Unknown → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-terminal - 2.22.1-0ubuntu1

---------------
gnome-terminal (2.22.1-0ubuntu1) hardy; urgency=low

  * New upstream bugfix release (LP: #213357)
    - Fix DetachTab action. (LP: #187358)
    - 02_autoconf.patch: updated

 -- Pedro Fragoso <email address hidden> Mon, 07 Apr 2008 14:04:39 +0100

Changed in gnome-terminal:
status: Fix Committed → Fix Released
Changed in gnome-terminal:
importance: Unknown → High
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.