Bug 407724 – crash in Terminal: stavo switchando i tab 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 407724 - crash in Terminal: stavo switchando i tab d...


Summary:	crash in Terminal: stavo switchando i tab d...


Status:	RESOLVED DUPLICATE of bug 348979

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-14 03:36 UTC by jaguarandi
Modified:	2007-02-14 16:22 UTC

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

Description jaguarandi 2007-02-14 03:36:23 UTC

Version: 2.16.1

What were you doing when the application crashed?
stavo switchando i tab del terminal con molti terminal aperti
I've switch between tabs of the Terminal white more terminals open
:)


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

Memory status: size: 63930368 vsize: 0 resident: 63930368 share: 0 rss: 20230144 rss_rlim: 0
CPU usage: start_time: 1171417133 rtime: 0 utime: 512 stime: 0 cutime:475 cstime: 0 timeout: 37 it_real_value: 0 frequency: 19

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 -1226197328 (LWP 13707)]
[New Thread -1255101536 (LWP 13711)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 110574

Thread 1 (Thread -1226197328 (LWP 13707))

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

Comment 1 Bruno Boaventura 2007-02-14 16:22:01 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 348979 ***