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 95102 - crashes when i resize (full screen)
crashes when i resize (full screen)
Status: RESOLVED DUPLICATE of bug 94509
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other Linux
: Normal critical
: ---
Assigned To: Havoc Pennington
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-10-07 18:45 UTC by henri
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description henri 2002-10-07 18:45:14 UTC
Description of Problem:

i'm ssh'ed into a rh7.2 box, running xemacs 21.4 
(terminal mode). click on "maximize" and the term
will crash.

Steps to reproduce the problem:
1. ssh into remote box
2. run xemacs -nw
3. maximize window

Actual Results:

i get the gnome crash dialog box

Expected Results:

a maximized window

How often does this happen? 

every time i do the above

Additional Information:

this only happens when i am logged into one
specific box. this doesn't seem to happen 
when i log into other machines.
Comment 1 Heath Harrelson 2002-10-25 23:02:30 UTC
Which version of gnome-terminal are you using?  Also, if possible,
could you follow the instructions in bug 96010 for getting a stack trace?
Comment 2 henri 2002-10-29 17:45:50 UTC
version: 

from the "about": 2.0.1
rpm: gnome-terminal-2.0.1-5

stock redhat 8 install.

stack trace:

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

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

Thread 1 (Thread 8192 (LWP 8084))

  • #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 3 John Fleck 2002-10-30 13:45:03 UTC
Thanks for the stack trace. This is a duplicate of bug 94509.

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