Bug 414861 – crash in Terminal: Starting Terminal after ...

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 414861 - crash in Terminal: Starting Terminal after ...


Summary:	crash in Terminal: Starting Terminal after ...


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-05 10:47 UTC by 4030168
Modified:	2007-03-21 18:25 UTC

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

Description 4030168 2007-03-05 10:47:32 UTC

Version: 2.16.0

What were you doing when the application crashed?
Starting Terminal after attempting to delete a folder created by SU.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 274092032 vsize: 274092032 resident: 18546688 share: 9269248 rss: 18546688 rss_rlim: -1
CPU usage: start_time: 1173090181 rtime: 189 utime: 176 stime: 13 cutime:233 cstime: 99 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496386528 (LWP 2892)]
[New Thread 1084229952 (LWP 2896)]
(no debugging symbols found)
0x00000035a9c0d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 115972

Thread 1 (Thread 46912496386528 (LWP 2892))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 gtk_widget_style_get_valist
from /usr/lib64/libgtk-x11-2.0.so.0
#4 gtk_widget_style_get
from /usr/lib64/libgtk-x11-2.0.so.0
#5 gtk_widget_style_get
from /usr/lib64/libgtk-x11-2.0.so.0
#6 gtk_widget_style_get
from /usr/lib64/libgtk-x11-2.0.so.0
#7 gtk_widget_queue_resize
from /usr/lib64/libgtk-x11-2.0.so.0
#8 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#9 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit
from /lib64/libgobject-2.0.so.0
#12 g_cclosure_marshal_VOID__OBJECT
#13 g_cclosure_marshal_VOID__OBJECT
#14 g_cclosure_marshal_VOID__OBJECT
#15 g_cclosure_marshal_VOID__OBJECT
#16 g_cclosure_marshal_VOID__OBJECT
#17 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#18 bonobo_closure_invoke_va_list
from /usr/lib64/libbonobo-2.so.0
#19 bonobo_closure_invoke
from /usr/lib64/libbonobo-2.so.0
#20 bonobo_listener_new
from /usr/lib64/libbonobo-2.so.0
#21 ORBit_small_invoke_adaptor
from /usr/lib64/libORBit-2.so.0
#22 ORBit_recv_buffer_return_sys_exception
from /usr/lib64/libORBit-2.so.0
#23 ORBit_recv_buffer_return_sys_exception
from /usr/lib64/libORBit-2.so.0
#24 ORBit_skel_class_register
from /usr/lib64/libORBit-2.so.0
#25 ORBit_handle_request
from /usr/lib64/libORBit-2.so.0
#26 giop_connection_handle_input
from /usr/lib64/libORBit-2.so.0
#27 link_connection_state_changed
from /usr/lib64/libORBit-2.so.0
#28 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#29 g_main_context_check
from /lib64/libglib-2.0.so.0
#30 g_main_loop_run
from /lib64/libglib-2.0.so.0
#31 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#32 g_cclosure_marshal_VOID__OBJECT
#33 __libc_start_main
from /lib64/libc.so.6
#34 g_cclosure_marshal_VOID__OBJECT
#35 ??
#36 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Christian Kirbach 2007-03-21 18:25:22 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 ***