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


Summary:	crash in Terminal:


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 23:08 UTC by aoki
Modified:	2007-01-11 22:14 UTC

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

Description aoki 2007-01-10 23:08:29 UTC

Version: 2.16.1

What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Rawhide)
Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.19-1.2906.fc7 #0 SMP Tue Jan 9 19:06:42 JST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled

Memory status: size: 267964416 vsize: 267964416 resident: 10375168 share: 8151040 rss: 10375168 rss_rlim: -1
CPU usage: start_time: 1168470505 rtime: 11 utime: 8 stime: 3 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 46912535492048 (LWP 3001)]
(no debugging symbols found)
0x0000003c8c80d7c5 in waitpid () from /lib64/libpthread.so.0

+ Trace 101110

Thread 1 (Thread 46912535492048 (LWP 3001))

#0 waitpid
from /lib64/libpthread.so.0
#1 libgnomeui_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
#4 g_cclosure_marshal_VOID__OBJECT
from /usr/lib64/libvte.so.9
#5 ??
#6 g_cclosure_marshal_VOID__OBJECT
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 /lib64/libgobject-2.0.so.0
#14 g_object_set
from /lib64/libgobject-2.0.so.0
#15 g_object_newv
from /lib64/libgobject-2.0.so.0
#16 g_object_new_valist
from /lib64/libgobject-2.0.so.0
#17 g_object_new
from /lib64/libgobject-2.0.so.0
#18 vte_terminal_new
from /usr/lib64/libvte.so.9
#19 g_cclosure_marshal_VOID__OBJECT
#20 g_cclosure_marshal_VOID__OBJECT
#21 g_type_create_instance
from /lib64/libgobject-2.0.so.0
#22 g_object_set
from /lib64/libgobject-2.0.so.0
#23 g_object_newv
from /lib64/libgobject-2.0.so.0
#24 g_object_new_valist
from /lib64/libgobject-2.0.so.0
#25 g_object_new
from /lib64/libgobject-2.0.so.0
#26 g_cclosure_marshal_VOID__OBJECT
#27 g_cclosure_marshal_VOID__OBJECT
#28 g_cclosure_marshal_VOID__OBJECT
#29 __libc_start_main
from /lib64/libc.so.6
#30 g_cclosure_marshal_VOID__OBJECT
#31 ??
#32 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 palfrey 2007-01-11 17:14:04 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 Susana 2007-01-11 17:28:18 UTC

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

Comment 3 Behdad Esfahbod 2007-01-11 22:14:16 UTC

Fixed in 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 ***