Bug 456836 – crash in Terminal: nothing

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 456836 - crash in Terminal: nothing


Summary:	crash in Terminal: nothing


Status:	RESOLVED DUPLICATE of bug 348979

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-07-14 11:29 UTC by mschoene
Modified:	2007-07-14 20:34 UTC

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

Description mschoene 2007-07-14 11:29:15 UTC

Version: 2.16.0

What were you doing when the application crashed?
nothing	


Distribution: Red Hat Enterprise Linux Client release 5 (Tikanga)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 136323072 vsize: 0 resident: 136323072 share: 0 rss: 28618752 rss_rlim: 0
CPU usage: start_time: 1184163277 rtime: 0 utime: 20651 stime: 0 cutime:18680 cstime: 0 timeout: 1971 it_real_value: 0 frequency: 90

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 -1209063728 (LWP 3267)]
[New Thread -1221350512 (LWP 3272)]
(no debugging symbols found)
0x00a11402 in __kernel_vsyscall ()

+ Trace 147968

Thread 1 (Thread -1209063728 (LWP 3267))

#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 g_type_check_is_value_type
from /lib/libgobject-2.0.so.0
#5 g_value_type_compatible
from /lib/libgobject-2.0.so.0
#6 g_object_class_override_property
from /lib/libgobject-2.0.so.0
#7 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#8 g_signal_emit
from /lib/libgobject-2.0.so.0
#9 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#10 gtk_widget_set_usize
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_widget_reset_rc_styles
from /usr/lib/libgtk-x11-2.0.so.0
#12 gtk_rc_get_module_dir
from /usr/lib/libgtk-x11-2.0.so.0
#13 gtk_icon_info_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#15 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#16 g_main_context_check
from /lib/libglib-2.0.so.0
#17 g_main_loop_run
from /lib/libglib-2.0.so.0
#18 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_cclosure_marshal_VOID__OBJECT
#20 __libc_start_main
from /lib/libc.so.6
#21 g_cclosure_marshal_VOID__OBJECT
#0 __kernel_vsyscall

Comment 1 Pedro Villavicencio 2007-07-14 20:34:05 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 348979 ***