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 115078 - gnome-terminal crashes
gnome-terminal crashes
Status: RESOLVED DUPLICATE of bug 105745
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Havoc Pennington
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-06-12 19:14 UTC by rcp
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description rcp 2003-06-13 05:16:48 UTC 
Package: gnome-terminal
Severity: normal
Version: 2.2.0.1
Synopsis: gnome-terminal crashes
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
Gnome terminal unexpectedly crashes, usually while another application
is used in the foreground.  I think this may only happen when I have a
gnome-terminal running with argument  '-e "expect somescript.exp"' where
somescript.exp is making a ssh2 connection to another host.  I think the
ssh2 connection which does port forwarding may be crashing and that
eventyally bringing down all of my gnome-terminals.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:
All gnome terminals die.

Expected Results:
Only the one gnome terminal with the ssh connection should die.

How often does this happen?
Once a day or so.

Additional Information:




Debugging Information:

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

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New
Thread 1086393248 (LWP 1464)]
0xffffe002 in ??
    ()

+ Trace 37767

Thread 1 (Thread 1086393248 (LWP 1464))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #5 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #6 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ?? 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-13 01:16 -------

The original reporter (rcp@slb.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, hp@redhat.com.
Comment 1 John Fleck 2003-06-15 14:38:20 UTC 
Is this a dup of bug 105745?
Comment 2 Elijah Newren 2003-07-04 20:01:38 UTC 
Yeah, the stack trace matches the one in bug 105762, which Mark
markeed as a duplicate of 105745.

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