Bug 408497 – crash in Terminal: th

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 408497 - crash in Terminal: th


Summary:	crash in Terminal: th


Status:	RESOLVED DUPLICATE of bug 397660

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-02-16 07:26 UTC by hammads_1999
Modified:	2008-04-04 13:24 UTC

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

Description hammads_1999 2007-02-16 07:26:13 UTC

Version: 2.16.0

What were you doing when the application crashed?
th


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 98594816 vsize: 0 resident: 98594816 share: 0 rss: 14512128 rss_rlim: 0
CPU usage: start_time: 1171607588 rtime: 0 utime: 545 stime: 0 cutime:478 cstime: 0 timeout: 67 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-terminal'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208310064 (LWP 2663)]
[New Thread -1214342256 (LWP 2667)]
(no debugging symbols found)
0x00233402 in __kernel_vsyscall ()

+ Trace 111177

Thread 1 (Thread -1208310064 (LWP 2663))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 re_search_internal
from /lib/libc.so.6
#5 regexec
from /lib/libc.so.6
#6 vte_terminal_accessible_new
from /usr/lib/libvte.so.9
#7 vte_terminal_get_text
from /usr/lib/libvte.so.9
#8 vte_terminal_get_text
from /usr/lib/libvte.so.9
#9 vte_terminal_get_text
from /usr/lib/libvte.so.9
#10 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#11 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /lib/libgobject-2.0.so.0
#13 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#15 g_signal_emit
from /lib/libgobject-2.0.so.0
#16 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#18 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#19 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#20 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#21 g_main_context_check
from /lib/libglib-2.0.so.0
#22 g_main_loop_run
from /lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_cclosure_marshal_VOID__OBJECT
#25 __libc_start_main
from /lib/libc.so.6
#26 g_cclosure_marshal_VOID__OBJECT
#0 __kernel_vsyscall

Comment 1 Mariano Suárez-Alvarez 2007-02-16 14:10:06 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 397660 ***

Comment 2 Cosimo Cecchi 2008-04-04 13:24:30 UTC

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