Bug 405123 – crash in Terminal: hit Ctrl d

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 405123 - crash in Terminal: hit Ctrl d


Summary:	crash in Terminal: hit Ctrl d


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:	2007-02-06 20:57 UTC by cezar
Modified:	2007-02-06 20:59 UTC

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

Description cezar 2007-02-06 20:57:47 UTC

Version: 2.16.1

What were you doing when the application crashed?
hit Ctrl d


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

Memory status: size: 93241344 vsize: 0 resident: 93241344 share: 0 rss: 12734464 rss_rlim: 0
CPU usage: start_time: 1170686772 rtime: 0 utime: 3927 stime: 0 cutime:2963 cstime: 0 timeout: 964 it_real_value: 0 frequency: 4936

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225902416 (LWP 11434)]
[New Thread -1250006112 (LWP 11438)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 108555

Thread 1 (Thread -1225902416 (LWP 11434))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_type_check_instance_is_a
from /usr/lib/libgobject-2.0.so.0
#5 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#6 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#7 _gtk_container_dequeue_resize_handler
from /usr/lib/libgtk-x11-2.0.so.0
#8 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#9 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#14 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_widget_hide
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#17 gtk_widget_unparent
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_notebook_set_window_creation_hook
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_notebook_new
from /usr/lib/libgtk-x11-2.0.so.0
#20 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#21 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#22 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#26 gtk_container_remove
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_notebook_remove_page
from /usr/lib/libgtk-x11-2.0.so.0
#28 ??
#29 ??
#30 ??
#0 __kernel_vsyscall

Comment 1 Mariano Suárez-Alvarez 2007-02-06 20:59:07 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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