Bug 417374 – 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 417374 - crash in Terminal:


Summary:	crash in Terminal:


Status:	RESOLVED DUPLICATE of bug 352444

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-12 08:00 UTC by unwiredbrain
Modified:	2007-03-13 01:03 UTC

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

Description unwiredbrain 2007-03-12 08:00:17 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: 147783680 vsize: 0 resident: 147783680 share: 0 rss: 83701760 rss_rlim: 0
CPU usage: start_time: 1173402672 rtime: 0 utime: 250961 stime: 0 cutime:224830 cstime: 0 timeout: 26131 it_real_value: 0 frequency: 25854

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 -1225980240 (LWP 2947)]
[New Thread -1273480288 (LWP 2954)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 117925

Thread 1 (Thread -1225980240 (LWP 2947))

#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 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 ORBit_RootObject_duplicate_T
from /usr/lib/libORBit-2.so.0
#11 CORBA_free
from /usr/lib/libORBit-2.so.0
#12 CORBA_free
from /usr/lib/libORBit-2.so.0
#13 ORBit_free_T
from /usr/lib/libORBit-2.so.0
#14 ORBit_free
from /usr/lib/libORBit-2.so.0
#15 CORBA_free
from /usr/lib/libORBit-2.so.0
#16 gnome_accessibility_module_shutdown
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#17 gnome_accessibility_module_shutdown
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#18 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 atk_object_notify_state_change
from /usr/lib/libatk-1.0.so.0
#22 gail_window_new
from /usr/lib/gtk-2.0/modules/libgail.so
#23 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#28 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#30 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#31 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#33 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#34 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#35 ??
#36 ??
#37 _IO_stdin_used
#38 ??
#39 ??
#0 __kernel_vsyscall

Comment 1 Susana 2007-03-13 01:03:41 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 352444 ***