Bug 395052 – crash in Terminal: application crashed at l...

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 395052 - crash in Terminal: application crashed at l...


Summary:	crash in Terminal: application crashed at l...


Status:	RESOLVED DUPLICATE of bug 394890

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-01-10 16:18 UTC by magnard
Modified:	2007-01-12 18:21 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description magnard 2007-01-10 16:18:19 UTC

Version: 2.16.1

What were you doing when the application crashed?
application crashed at launching


Distribution: Mandriva Linux release 2007.1 (Cooker) for x86_64
Gnome Release: 2.17.5 2007-01-09 (Mandriva)
BugBuddy Version: 2.17.3

System: Linux 2.6.19.1-tmb-desktop-4mdvsmp #1 SMP Tue Jan 2 06:56:52 EST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled

Memory status: size: 130981888 vsize: 130981888 resident: 10498048 share: 8216576 rss: 10498048 rss_rlim: -1
CPU usage: start_time: 1168445851 rtime: 7 utime: 6 stime: 1 cutime:0 cstime: 0 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 47903845478800 (LWP 21217)]
(no debugging symbols found)
0x00002b917ad22dd5 in waitpid () from /lib64/libpthread.so.0

+ Trace 101003

#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 ??
#4 ??
from /usr/lib64/libvte.so.9
#5 ??
#6 ??
from /usr/lib64/libvte.so.9
#7 ??
#8 ??
#9 vte_terminal_accessible_new
from /usr/lib64/libvte.so.9
#10 _vte_debug_parse_string
from /usr/lib64/libvte.so.9
#11 vte_terminal_set_emulation
from /usr/lib64/libvte.so.9
#12 vte_terminal_feed_child
from /usr/lib64/libvte.so.9
#13 g_type_create_instance
from /usr/lib64/libgobject-2.0.so.0
#14 g_object_set
from /usr/lib64/libgobject-2.0.so.0
#15 g_object_newv
from /usr/lib64/libgobject-2.0.so.0
#16 g_object_new_valist
from /usr/lib64/libgobject-2.0.so.0
#17 g_object_new
from /usr/lib64/libgobject-2.0.so.0
#18 vte_terminal_new
from /usr/lib64/libvte.so.9
#19 ??
#20 ??
#21 g_type_create_instance
from /usr/lib64/libgobject-2.0.so.0
#22 g_object_set
from /usr/lib64/libgobject-2.0.so.0
#23 g_object_newv
from /usr/lib64/libgobject-2.0.so.0
#24 g_object_new_valist
from /usr/lib64/libgobject-2.0.so.0
#25 g_object_new
from /usr/lib64/libgobject-2.0.so.0
#26 ??
#27 ??
#28 ??
#29 __libc_start_main
from /lib64/libc.so.6
#30 ??
#31 ??
#32 ??


Thread 1 (Thread 47903845478800 (LWP 21217)):
#-1 0x00002b917ad22dd5 in waitpid () from /lib64/libpthread.so.0
No symbol table info available.


----------- .xsession-errors ---------------------
event->keyval: 108, event->state:0
Not mathced
subset is whole list!
event->keyval: 65293, event->state:0
Not mathced
GTK Accessibility Module initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
Backtrace limit of 200 exceeded
Backtrace limit of 200 exceeded
Backtrace limit of 200 exceeded
--------------------------------------------------

Comment 1 palfrey 2007-01-12 01:27:21 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 magnard 2007-01-12 18:11:07 UTC

(In reply to comment #1)
> Can you get us a stack trace with debugging symbols? Please see

Hello,
The crashing bug went away with a daily upgrade of mandriva cooker.
Sorry I could not reproduce it !

Fred.

Comment 3 Behdad Esfahbod 2007-01-12 18:21:16 UTC

Yeah, fixed in vte trunk.Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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