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 59260 - gnome-terminal crashes when moving mouse pointer while text is being written
gnome-terminal crashes when moving mouse pointer while text is being written
Status: RESOLVED DUPLICATE of bug 50636
Product: gnome-core
Classification: Deprecated
Component: gnome-terminal
unspecified
Other other
: Normal critical
: ---
Assigned To: gnome-core Maintainers
gnome-core Maintainers
Depends on:
Blocks:
 
 
Reported: 2001-08-20 16:09 UTC by sjn+gnome
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description sjn+gnome 2001-08-20 16:09:16 UTC 
Package: gnome-core
Severity: critical
Version: 1.4.0.4
Synopsis: gnome-terminal crashes when moving mouse pointer while text is being written
Bugzilla-Product: gnome-core
Bugzilla-Component: gnome-terminal

Description:
I've submitted this bug before (dont know the buf-id, though), and at that time I thought it had something to do with the handling of terminal capabilities (by screen(1) or when connecting to an AIX server I'm using), but I'm not very sure about this.

I cannot reproduce the crash in a consistent manner, but if someone can point me to a binary with the debugging-symbols enabled (or a guide on how to build it) I can see if that helps.

Generally, gnome-terminal crashes when I get some output (regardless wether I use screen(1) or not), while I'm moving the mouse cursor. This bug _does_ occur _much_ more often when connecting to a FreeBSD-box running screen(1) in which i connect to the AIX server, than in any other case. I'm also running a screen on another server (Linux) with shells on FreeBSD and Linux boxes, but that one has never crashed.

The crashing gets a bit irritating when it happens 10 times an hour :-(

Please notify if you need any help in tracking this bug down - I'll be glad to help! :)


Debugging Information:

(no debugging symbols found)...0x40643519 in __wait4 ()
   from /lib/i686/libc.so.6

+ Trace 8673

  • #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-08-20 12:09 -------

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 19:01:03 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 ***