Bug 423864 – crash in Terminal: Arrancando el sistema

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 423864 - crash in Terminal: Arrancando el sistema


Summary:	crash in Terminal: Arrancando el sistema


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-28 19:46 UTC by fblesla
Modified:	2007-03-31 14:11 UTC

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

Description fblesla 2007-03-28 19:46:26 UTC

Version: 2.16.1

What were you doing when the application crashed?
Arrancando el sistema


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

Memory status: size: 20398080 vsize: 0 resident: 20398080 share: 0 rss: 7102464 rss_rlim: 0
CPU usage: start_time: 1175110878 rtime: 0 utime: 5 stime: 0 cutime:4 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0

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 -1226725712 (LWP 4614)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 123005

Thread 1 (Thread -1226725712 (LWP 4614))

#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 ORBit_free_T
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 bonobo_activation_object_directory_get
from /usr/lib/libbonobo-activation.so.4
#17 bonobo_activation_register_client
from /usr/lib/libbonobo-activation.so.4
#18 bonobo_activation_internal_service_get_extended
from /usr/lib/libbonobo-activation.so.4
#19 bonobo_activation_service_get
from /usr/lib/libbonobo-activation.so.4
#20 bonobo_activation_activation_context_get
from /usr/lib/libbonobo-activation.so.4
#21 bonobo_activation_object_directory_get
from /usr/lib/libbonobo-activation.so.4
#22 bonobo_activation_register_active_server_ext
from /usr/lib/libbonobo-activation.so.4
#23 bonobo_activation_register_active_server
from /usr/lib/libbonobo-activation.so.4
#24 bonobo_activation_active_server_register
from /usr/lib/libbonobo-activation.so.4
#25 ??
#26 ??
#27 ??
#28 __after_morecore_hook
from /lib/tls/i686/cmov/libc.so.6
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#0 __kernel_vsyscall

Comment 1 André Klapper 2007-03-31 14:11:09 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 ask Ubuntu for a software upgrade.


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