Bug 413598 – crash in Terminal: It crached while i was s...

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 413598 - crash in Terminal: It crached while i was s...


Summary:	crash in Terminal: It crached while i was s...


Status:	RESOLVED DUPLICATE of bug 353498

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-03-01 20:25 UTC by pawelziolo
Modified:	2007-03-02 01:27 UTC

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

Description pawelziolo 2007-03-01 20:25:49 UTC

Version: 2.16.1

What were you doing when the application crashed?
It crached while i was switching application theme 


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

Memory status: size: 43102208 vsize: 0 resident: 43102208 share: 0 rss: 15925248 rss_rlim: 0
CPU usage: start_time: 1172776173 rtime: 0 utime: 546 stime: 0 cutime:476 cstime: 0 timeout: 70 it_real_value: 0 frequency: 28

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 -1226193232 (LWP 15492)]
[New Thread -1247913056 (LWP 15496)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 115014

Thread 1 (Thread -1226193232 (LWP 15492))

#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_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#7 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_box_pack_start_defaults
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_container_forall
from /usr/lib/libgtk-x11-2.0.so.0
#10 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_widget_style_get
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_widget_queue_resize
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_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_button_box_set_child_size
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_widget_reset_rc_styles
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_rc_get_theme_dir
from /usr/lib/libgtk-x11-2.0.so.0
#20 gtk_rc_reparse_all_for_settings
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_rc_reparse_all
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_cclosure_marshal_VOID__PARAM
from /usr/lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#27 g_object_class_override_property
from /usr/lib/libgobject-2.0.so.0
#28 g_enum_register_static
from /usr/lib/libgobject-2.0.so.0
#29 g_object_notify
from /usr/lib/libgobject-2.0.so.0
#30 _gtk_settings_handle_event
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#32 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#33 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#34 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#35 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#36 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#37 ??
#38 ??
#39 _IO_stdin_used
#40 ??
#41 ??
#0 __kernel_vsyscall

Comment 1 Bruno Boaventura 2007-03-02 01:27:11 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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