Bug 105065 – gnome-terminal crash when using Mutt

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 105065 - gnome-terminal crash when using Mutt


Summary:	gnome-terminal crash when using Mutt


Status:	RESOLVED DUPLICATE of bug 94509

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Havoc Pennington
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-02-02 20:39 UTC by steve
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description steve 2003-02-02 20:35:38 UTC

Package: gnome-terminal
Severity: normal
Version: 2.0.1
Synopsis: gnome-terminal crash when using Mutt
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
This crash happens a lot, but I haven't figured out how to reliably
reproduce it.
It usually involves having multiple tabs open.  One of the tabs has an
ssh session
to another Linux box.  In that ssh session, I'll be running Mutt.  When
I try to reply
to an e-mail (or some other Mutt function), gnome-terminal dies.

One more detail, that is probably important, is that I've usually
re-sized the
gnome-terminal after starting Mutt.  Oh, and the ssh session usually
goes
through an old Sparc 10 before reaching the Linux box (not sure if that
matters).

Steps to reproduce the problem:
1.  start gnome-terminal, open multiple tabs
2.  ssh to another machine, start mutt
3.  resize the terminal window, then try replying to an e-mail.

Actual Results:


Expected Results:


How often does this happen?
Often, but not reliably

Additional Information:




Debugging Information:

Backtrace was generated from '/usr/bin/gnome-terminal'

(no debugging symbols found)...[New Thread 8192 (LWP 20985)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 33411

Thread 1 (Thread 8192 (LWP 20985))

#0 wait4
from /lib/i686/libc.so.6
#1 __DTOR_END__
from /lib/i686/libc.so.6
#2 waitpid
from /lib/i686/libpthread.so.0
#3 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#4 __pthread_sighandler
from /lib/i686/libpthread.so.0
#5 <signal handler called>
#6 kill
from /lib/i686/libc.so.6
#7 raise
from /lib/i686/libpthread.so.0
#8 abort
from /lib/i686/libc.so.6
#9 g_logv
from /usr/lib/libglib-2.0.so.0
#10 g_log
from /usr/lib/libglib-2.0.so.0
#11 vte_terminal_ensure_cursor
from /usr/lib/libvte.so.2
#12 vte_terminal_insert_char
from /usr/lib/libvte.so.2
#13 vte_terminal_process_incoming
from /usr/lib/libvte.so.2
#14 g_idle_dispatch
from /usr/lib/libglib-2.0.so.0
#15 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#18 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#19 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#20 main
#21 __libc_start_main
from /lib/i686/libc.so.6
#0 wait4
from /lib/i686/libc.so.6





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-02 15:35 -------

The original reporter (steve@borho.org) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, hp@redhat.com.

Comment 1 Alex Duggan 2003-02-02 21:41:55 UTC


*** This bug has been marked as a duplicate of 94509 ***