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 56636 - Repetitive crashes with gnome-terminal
Repetitive crashes with gnome-terminal
Status: RESOLVED DUPLICATE of bug 50636
Product: gnome-core
Classification: Deprecated
Component: gnome-terminal
unspecified
Other other
: Normal normal
: ---
Assigned To: gnome-core Maintainers
gnome-core Maintainers
Depends on:
Blocks:
 
 
Reported: 2001-06-25 10:52 UTC by sjn+gnome
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description sjn+gnome 2001-06-25 10:52:38 UTC
Package: gnome-core
Severity: normal
Version: 1.4.0.4
Synopsis: Repetitive crashes with gnome-terminal
Bugzilla-Product: gnome-core
Bugzilla-Component: gnome-terminal

Description:
I can''t seem to reproduce the crash in a predictable manner.

I do the foolowing things:

 1. start gnome-terminal (often several, using the right-click menu in g-t)
 2. ssh to a remote FreeBSD machine with redhat's openssh RPM, using the following command:

    $ /usr/bin/ssh -c blowfish -C -L1120:news.somewhere.close:119 freebsd.workplace.locally

 3. I start/resume a screen session (Screen version 3.09.05 (FAU) 1-Sep-99), where I ssh to a remote AIX 4.3 server, using SSH Version 1.2.27 [i386-unknown-freebsd4.1]. 

after a while of typing, screen changing, command execution, editing and similar common tasks, gnome-terminal crashes, taking with it any other terminals I've started through the menu.

It's quite irritating (this happens to me a couple of times every day)

Hope this helps! :)


Debugging Information:

(no debugging symbols found)...0x40642519 in __wait4 ()
   from /lib/i686/libc.so.6
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 gnome_segv_handle
    at gnome-init.c line 659
  • #3 <signal handler called>
  • #4 vt_getmatches
    at update.c line 1570
  • #5 zvt_term_motion_notify
    at zvtterm.c line 1833
  • #6 gtk_marshal_BOOL__POINTER
    at gtkmarshal.c line 28
  • #7 gtk_signal_real_emit
    at gtksignal.c line 1492
  • #8 gtk_signal_emit
    at gtksignal.c line 552
  • #9 gtk_widget_event
    at gtkwidget.c line 2864
  • #10 gtk_propagate_event
    at gtkmain.c line 1378
  • #11 gtk_main_do_event
    at gtkmain.c line 818
  • #12 gdk_event_dispatch
    at gdkevents.c line 2139
  • #13 g_main_dispatch
    at gmain.c line 656
  • #14 g_main_iterate
    at gmain.c line 877
  • #15 g_main_run
    at gmain.c line 935
  • #16 gtk_main
    at gtkmain.c line 524
  • #17 new_terminal_for_client
    at eval.c line 41
  • #18 main
    at eval.c line 41
  • #19 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 129
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 gnome_segv_handle
    at gnome-init.c line 659
  • #3 <signal handler called>
  • #4 vt_getmatches
    at update.c line 1570
  • #5 zvt_term_motion_notify
    at zvtterm.c line 1833
  • #6 gtk_marshal_BOOL__POINTER
    at gtkmarshal.c line 28
  • #7 gtk_signal_real_emit
    at gtksignal.c line 1492




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-06-25 06:52 -------

The original reporter (sjn+gnome@tinde.com) 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, gnome-core-maint@bugzilla.gnome.org.

Comment 1 Kjartan Maraas 2001-08-27 18:58:15 UTC
This might have been caused by bugs in regexp handing in glibc. Can
you try upgrading glibc and see if that helps?


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