Bug 395247 – crash in Terminal: opening gnome-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 395247 - crash in Terminal: opening gnome-terminal


Summary:	crash in Terminal: opening gnome-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-11 01:46 UTC by John Ellson
Modified:	2007-01-11 22:18 UTC

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

Description John Ellson 2007-01-11 01:46:43 UTC

Version: 2.16.1

What were you doing when the application crashed?
opening gnome-terminal


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.17-1.2548.fc6 #1 SMP Thu Aug 10 22:30:10 EDT 2006 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Permissive
Accessibility: Disabled

Memory status: size: 251682816 vsize: 251682816 resident: 8880128 share: 7065600 rss: 8880128 rss_rlim: -1
CPU usage: start_time: 1168479943 rtime: 6 utime: 3 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 46912535590352 (LWP 23424)]
(no debugging symbols found)
0x000000385f60d7c5 in waitpid () from /lib64/libpthread.so.0

+ Trace 101142

Thread 1 (Thread 46912535590352 (LWP 23424))

#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 Susana 2007-01-11 17:21:17 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 395222 ***

Comment 2 Behdad Esfahbod 2007-01-11 22:18:12 UTC

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