Bug 438793 – crash in Gnome Terminal: sleeping

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 438793 - crash in Gnome Terminal: sleeping


Summary:	crash in Gnome Terminal: sleeping


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-05-16 05:29 UTC by tony.yates
Modified:	2007-06-20 21:49 UTC

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

Description tony.yates 2007-05-16 05:29:24 UTC

Version: 2.16.1

What were you doing when the application crashed?
sleeping


Distribution: openSUSE 10.2 (i586)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 105201664 vsize: 0 resident: 105201664 share: 0 rss: 73265152 rss_rlim: 0
CPU usage: start_time: 1178689766 rtime: 0 utime: 15455 stime: 0 cutime:7730 cstime: 0 timeout: 7725 it_real_value: 0 frequency: 0

Backtrace was generated from '/opt/gnome/bin/gnome-terminal'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227204928 (LWP 5431)]
[New Thread -1233544304 (LWP 5438)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 134395

Thread 1 (Thread -1227204928 (LWP 5431))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /opt/gnome/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 g_logv
from /opt/gnome/lib/libglib-2.0.so.0
#8 g_log
from /opt/gnome/lib/libglib-2.0.so.0
#9 g_assert_warning
from /opt/gnome/lib/libglib-2.0.so.0
#10 ORBit_RootObject_duplicate_T
from /opt/gnome/lib/libORBit-2.so.0
#11 CORBA_free
from /opt/gnome/lib/libORBit-2.so.0
#12 CORBA_free
from /opt/gnome/lib/libORBit-2.so.0
#13 ORBit_free_T
from /opt/gnome/lib/libORBit-2.so.0
#14 ORBit_free
from /opt/gnome/lib/libORBit-2.so.0
#15 CORBA_free
from /opt/gnome/lib/libORBit-2.so.0
#16 gnome_accessibility_module_shutdown
from /opt/gnome/lib/gtk-2.0/modules/libatk-bridge.so
#17 gnome_accessibility_module_shutdown
from /opt/gnome/lib/gtk-2.0/modules/libatk-bridge.so
#18 g_signal_override_class_closure
from /opt/gnome/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /opt/gnome/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /opt/gnome/lib/libgobject-2.0.so.0
#21 atk_object_notify_state_change
from /opt/gnome/lib/libatk-1.0.so.0
#22 vte_terminal_accessible_get_type
from /opt/gnome/lib/libvte.so.9
#23 gtk_marshal_BOOLEAN__VOID
from /opt/gnome/lib/libgtk-x11-2.0.so.0
#24 g_closure_invoke
from /opt/gnome/lib/libgobject-2.0.so.0
#25 g_signal_override_class_closure
from /opt/gnome/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /opt/gnome/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /opt/gnome/lib/libgobject-2.0.so.0
#28 gtk_widget_get_default_style
from /opt/gnome/lib/libgtk-x11-2.0.so.0
#29 gtk_main_do_event
from /opt/gnome/lib/libgtk-x11-2.0.so.0
#30 gdk_add_client_message_filter
from /opt/gnome/lib/libgdk-x11-2.0.so.0
#31 g_main_context_dispatch
from /opt/gnome/lib/libglib-2.0.so.0
#32 g_main_context_prepare
from /opt/gnome/lib/libglib-2.0.so.0
#33 g_main_loop_run
from /opt/gnome/lib/libglib-2.0.so.0
#34 gtk_main
from /opt/gnome/lib/libgtk-x11-2.0.so.0
#35 g_cclosure_marshal_VOID__OBJECT
#36 ??
#37 _IO_stdin_used
#38 g_cclosure_marshal_VOID__OBJECT
#39 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-06-20 21:49:43 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 ***