Bug 381997 – crash in Terminal: updating with yum. mozil...

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 381997 - crash in Terminal: updating with yum. mozil...


Summary:	crash in Terminal: updating with yum. mozil...


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:	2006-12-03 20:43 UTC by benoit.gremaud
Modified:	2006-12-03 20:49 UTC

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

Description benoit.gremaud 2006-12-03 20:43:37 UTC

Version: 2.16.0

What were you doing when the application crashed?
updating with yum.
mozilla was running


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: 327938048 vsize: 327938048 resident: 18223104 share: 8941568 rss: 18223104 rss_rlim: -1
CPU usage: start_time: 1165177502 rtime: 315 utime: 259 stime: 56 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 46912496370128 (LWP 2700)]
[New Thread 1084229952 (LWP 2804)]
(no debugging symbols found)
0x0000003c7c60d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 91356

Thread 1 (Thread 46912496370128 (LWP 2700))

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

Comment 1 Christian Kirbach 2006-12-03 20:49:28 UTC

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