Bug 110338 – gnome-terminal crashes when resizing the window if running less

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 110338 - gnome-terminal crashes when resizing the window if running less


Summary:	gnome-terminal crashes when resizing the window if running less


Status:	RESOLVED DUPLICATE of bug 94509

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-04-08 23:32 UTC by Daniel Brice
Modified:	2004-12-22 21:47 UTC

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

Description Daniel Brice 2003-04-08 23:32:02 UTC

Description:
Description of Problem:
If I'm viewing a file with 'less' and resize the terminal window,
gnome-terminal will crash.

Steps to reproduce the problem:
1. Start with a gnome-terminal window with a size of 80x25 characters.
2. View a large text file with the less command in the terminal.
3. Resize the terminal to be much larger (e.g. 140x50)

Actual Results:
That gnome-terminal and all it's other terminal windows will crash.

Expected Results:
The window should resize, and less will instatly update the screen
displaying the file formatted for the new width and height.

How often does this happen?
I think it's every time I try to resize the window when I'm running
less. I've never seen it happen when I'm not running less in the
terminal window that I resize.  It also doesn't seem to matter where I'm
running less from - local on my computer or remotely using rlogin on
another machine.  I doubt it's an issue with less.

Additional Information:




Debugging Information:

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

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

+ Trace 35746

Thread 1 (Thread 8192 (LWP 3828))

#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_sequence_handler_ce
from /usr/lib/libvte.so.2
#13 vte_terminal_handle_sequence
from /usr/lib/libvte.so.2
#14 vte_terminal_process_incoming
from /usr/lib/libvte.so.2
#15 g_idle_dispatch
from /usr/lib/libglib-2.0.so.0
#16 g_main_dispatch
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 main
#22 __libc_start_main
from /lib/i686/libc.so.6
#0 wait4
from /lib/i686/libc.so.6

Comment 1 John Fleck 2003-04-09 14:36:37 UTC

This should be fixed by an upgrade to your vte and gnome-terminal.

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