Bug 371030 – crash in Terminal: neeeeeeeeeeiiinnnn.... h...

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 371030 - crash in Terminal: neeeeeeeeeeiiinnnn.... h...


Summary:	crash in Terminal: neeeeeeeeeeiiinnnn.... h...


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:

Duplicates:	411202 414446 415314 418947 (view as bug list)
Depends on:
Blocks:

Reported:	2006-11-05 13:58 UTC by stefan
Modified:	2007-03-16 13:11 UTC

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

Description stefan 2006-11-05 13:58:17 UTC

Version: 2.16.1

What were you doing when the application crashed?
neeeeeeeeeeiiinnnn....
hab n programm programmiert des wenig ram und viel cpu braucht. läuft jetzt schon seit 5 stunden... aber jetzt isses hängengeblieben :( vermutlich weil der bildschirm nach 15min inaktivität abgeschaltet hat


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

Memory status: size: 170307584 vsize: 0 resident: 170307584 share: 0 rss: 88477696 rss_rlim: 0
CPU usage: start_time: 1162718568 rtime: 0 utime: 33370 stime: 0 cutime:28865 cstime: 0 timeout: 4505 it_real_value: 0 frequency: 251

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 -1225902416 (LWP 25318)]
[New Thread -1277162592 (LWP 25322)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 83200

Thread 1 (Thread -1225902416 (LWP 25318))

#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 André Klapper 2006-11-05 14:05:46 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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

Comment 2 palfrey 2007-02-23 14:14:46 UTC

*** Bug 411202 has been marked as a duplicate of this bug. ***

Comment 3 Susana 2007-03-04 13:19:36 UTC

*** Bug 414446 has been marked as a duplicate of this bug. ***

Comment 4 Susana 2007-03-07 12:35:53 UTC

*** Bug 415314 has been marked as a duplicate of this bug. ***

Comment 5 Pedro Villavicencio 2007-03-16 13:11:07 UTC

*** Bug 418947 has been marked as a duplicate of this bug. ***