Bug 103765 – Gnome terminal crashes on resize

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 103765 - Gnome terminal crashes on resize


Summary:	Gnome terminal crashes on resize


Status:	RESOLVED DUPLICATE of bug 94735

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.0.x
Hardware:	Other Windows

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-01-17 18:41 UTC by Nathan
Modified:	2004-12-22 21:47 UTC

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

Description Nathan 2003-01-17 18:41:33 UTC

I started a gnome-terminal, SSH'ed to another box. I was reading man 
pages, then tried to resize (larger) the terminal and it crashed.  This 
problem is repeatable.

Comment 1 Alex Duggan 2003-01-17 21:14:51 UTC

Please include a backtrace of the crash using bug-buddy or gdb.  See
http://bugzilla.gnome.org/getting-traces.cgi for more information. 
Thanks.

Comment 2 kdd 2003-02-04 19:24:51 UTC

** ERROR **: NULL at 30(->1) delta 32, length 27, max 29 next 59 at 2376

Comment 3 kdd 2003-02-04 19:44:45 UTC

(sorry incomplete - output to  standard error).   I have the same
crash behavior on resizing for ssh, occasionally rsh.  

gdb output:
** ERROR **: NULL at 111(->55) delta 129, length 38, max 56 next 167
at 2376

aborting...

Program received signal SIGABRT, Aborted.

+ Trace 33480

Thread 8192 (LWP 3189)

#0 kill
from /lib/i686/libc.so.6
#1 raise
from /lib/i686/libpthread.so.0
#2 abort
from /lib/i686/libc.so.6
#3 g_logv
from /usr/lib/libglib-2.0.so.0
#4 g_log
from /usr/lib/libglib-2.0.so.0
#5 vte_terminal_ensure_cursor
from /usr/lib/libvte.so.2
#6 vte_sequence_handler_ce
from /usr/lib/libvte.so.2
#7 vte_terminal_handle_sequence
from /usr/lib/libvte.so.2
#8 vte_terminal_process_incoming
from /usr/lib/libvte.so.2
#9 g_idle_dispatch
from /usr/lib/libglib-2.0.so.0
#10 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#13 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#14 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#15 main
#16 __libc_start_main
from /lib/i686/libc.so.6


I can not reproduce this on a friend's vanilla RH8.0, so I suspect a
LANG or font change  is behind it.

Comment 4 Nathan 2003-02-04 20:58:34 UTC

This time I SSH'ed to another box, executed the command "ls -al |
less" while it was still pageing, I resized the window. Here are the
results: 

(gdb) run
Starting program: /usr/bin/gnome-terminal 
[New Thread 8192 (LWP 1354)]

** ERROR **: NULL at 18(->18) delta 21, length 29, max 32 next 50 at 2376

aborting...

Program received signal SIGABRT, Aborted.
[Switching to Thread 8192 (LWP 1354)]
0x42028cc1 in kill () from /lib/i686/libc.so.6
(gdb) thread apply all bt

+ Trace 33483

Thread 1 (Thread 8192 (LWP 1354))

#0 kill
from /lib/i686/libc.so.6
#1 raise
from /lib/i686/libpthread.so.0
#2 abort
from /lib/i686/libc.so.6
#3 g_logv
from /usr/lib/libglib-2.0.so.0
#4 g_log
from /usr/lib/libglib-2.0.so.0
#5 vte_terminal_ensure_cursor
from /usr/lib/libvte.so.2
#6 vte_sequence_handler_ce
from /usr/lib/libvte.so.2
#7 vte_terminal_handle_sequence
from /usr/lib/libvte.so.2
#8 vte_terminal_process_incoming
from /usr/lib/libvte.so.2
#9 g_idle_dispatch
from /usr/lib/libglib-2.0.so.0
#10 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#13 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#14 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#15 main
#16 __libc_start_main
from /lib/i686/libc.so.6

Comment 5 Alex Duggan 2003-02-05 03:29:40 UTC


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