Bug 362237 – crash in Terminal: I open a ssh connection ...

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 362237 - crash in Terminal: I open a ssh connection ...


Summary:	crash in Terminal: I open a ssh connection ...


Status:	RESOLVED DUPLICATE of bug 361117

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-14 23:10 UTC by Ikipou
Modified:	2006-10-15 17:06 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Ikipou 2006-10-14 23:10:27 UTC

Version: 2.16.1

What were you doing when the application crashed?
I open a ssh connection to a server then another connexion from that server to an other server in an intranet. I close the connexion by hitting several times Ctrl-D and the last Ctrl-D to finish the local terminal lead to the crash.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 145735680 vsize: 145735680 resident: 21749760 share: 11907072 rss: 21749760 rss_rlim: -1
CPU usage: start_time: 1160854951 rtime: 512 utime: 386 stime: 126 cutime:541 cstime: 2914 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912595625616 (LWP 17405)]
[New Thread 1082132816 (LWP 17410)]
(no debugging symbols found)
0x00002aaaac6ddeef in waitpid () from /lib/libpthread.so.0

+ Trace 76352

Thread 1 (Thread 46912595625616 (LWP 17405))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_type_check_instance_is_a
from /usr/lib64/libgobject-2.0.so.0
#4 g_object_unref
from /usr/lib64/libgobject-2.0.so.0
#5 gtk_widget_get_default_style
from /usr/lib64/libgtk-x11-2.0.so.0
#6 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#7 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#8 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#9 g_signal_emit
from /usr/lib64/libgobject-2.0.so.0
#10 gtk_object_destroy
from /usr/lib64/libgtk-x11-2.0.so.0
#11 g_object_unref
from /usr/lib64/libgobject-2.0.so.0
#12 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#13 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#15 g_signal_emit_by_name
from /usr/lib64/libgobject-2.0.so.0
#16 g_closure_invoke
from /usr/lib64/libgobject-2.0.so.0
#17 g_signal_chain_from_overridden
from /usr/lib64/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /usr/lib64/libgobject-2.0.so.0
#19 g_signal_emit_by_name
from /usr/lib64/libgobject-2.0.so.0
#20 g_source_is_destroyed
from /usr/lib64/libglib-2.0.so.0
#21 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#22 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#23 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#24 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#25 ??
#26 __libc_start_main
from /lib/libc.so.6
#27 ??
#28 ??
#29 ??
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Baptiste Mille-Mathias 2006-10-15 17:06:15 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 361117 ***