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 115458 - Gnome Terminal crashes when resizing less, pine, etc
Gnome Terminal crashes when resizing less, pine, etc
Status: RESOLVED DUPLICATE of bug 94509
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: Normal critical
: ---
Assigned To: Havoc Pennington
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-06-18 14:57 UTC by cce3
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description cce3 2003-06-18 14:57:09 UTC 
Package: gnome-terminal
Severity: critical
Version: 2.0.1
Synopsis: Gnome Terminal crashes when resizing less, pine, etc
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
Resizing windows causes gnome terminal to crash.  Since all terminals
run together, you don't just lose the terminal you were resizing, but
ALL terminals you had open.  I'm a programmer and usually have dozens of
terminals open -- this is a complete show-stopper for me and makes
gnome-terminal completely unusable.  IMO this is a huge bug, as most
people assume they can trust at least their terminal to be stable.

Steps to reproduce the problem:
1. Open a file in less, or run pine.  It may help to ssh to a remote
host first. 
2. Resize the window.
3. With pine over SSH the crash comes immediately.  With less, it
depends on how fast you resize the window and how long (?) the file
you've got open is.  Try opening less/pine over SSH and resizing the
terminal quickly, from very small to very big if you can't reproduce it
right away.

Actual Results:
stderr says:
** ERROR **: NULL at 561(->0) delta 562, length 2, max 3 next 564 at
2376

Expected Results:
The window resizes normally, and I don't lose any work I had open in my
terminals.

How often does this happen?
EVERY TIME I resize pine over SSH in gnome-terminal, and very often when
I resize less of SSH.

Additional Information:




Debugging Information:

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

(no debugging symbols found)...[New Thread 16384 (LWP 14574)]
0x408f27f7 in waitpid () from /lib/i686/libpthread.so.0

+ Trace 37940

Thread 1 (Thread 16384 (LWP 14574))

  • #0 waitpid
    from /lib/i686/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #3 <signal handler called>
  • #4 kill
    from /lib/i686/libc.so.6
  • #5 raise
    from /lib/i686/libpthread.so.0
  • #6 raise
    from /lib/i686/libc.so.6
  • #7 abort
    from /lib/i686/libc.so.6
  • #8 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #9 g_log
    from /usr/lib/libglib-2.0.so.0
  • #10 vte_terminal_ensure_cursor
    from /usr/lib/libvte.so.2
  • #11 vte_sequence_handler_ce
    from /usr/lib/libvte.so.2
  • #12 vte_terminal_handle_sequence
    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 waitpid
    from /lib/i686/libpthread.so.0 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-18 10:57 -------

Reassigning to the default owner of the component, hp@redhat.com.
Comment 1 Elijah Newren 2003-06-20 05:00:13 UTC 
Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs you find.

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