Bug 387959 – crash in Terminal:

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 387959 - crash in Terminal:


Summary:	crash in Terminal:


Status:	RESOLVED DUPLICATE of bug 355453

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-12-20 17:14 UTC by tobias.heinemann
Modified:	2006-12-20 17:16 UTC

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

Description tobias.heinemann 2006-12-20 17:14:54 UTC

Version: 2.16.1

What were you doing when the application crashed?



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

Memory status: size: 56942592 vsize: 0 resident: 56942592 share: 0 rss: 16031744 rss_rlim: 0
CPU usage: start_time: 1166633803 rtime: 0 utime: 204 stime: 0 cutime:177 cstime: 0 timeout: 27 it_real_value: 0 frequency: 102

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 -1225922896 (LWP 14052)]
[New Thread -1250931808 (LWP 14056)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 95714

Thread 1 (Thread -1225922896 (LWP 14052))

#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 gtk_widget_style_get_valist
from /usr/lib/libgtk-x11-2.0.so.0
#5 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#6 gtk_scrollbar_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#7 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#8 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#13 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_box_pack_start_defaults
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_button_box_set_child_size
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_notebook_popup_enable
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_box_pack_start_defaults
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_button_box_set_child_size
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_widget_reset_rc_styles
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_rc_get_theme_dir
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_icon_info_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#33 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#34 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#35 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#36 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#37 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#38 ??
#39 ??
#40 _IO_stdin_used
#41 ??
#42 ??
#0 __kernel_vsyscall

Comment 1 Mariano Suárez-Alvarez 2006-12-20 17:16:18 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 355453 ***