Bug 365260 – crash in Terminal: yum

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 365260 - crash in Terminal: yum


Summary:	crash in Terminal: yum


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-10-26 12:51 UTC by suwodanjer
Modified:	2006-11-01 23:34 UTC

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

Description suwodanjer 2006-10-26 12:51:09 UTC

Version: 2.16.0

What were you doing when the application crashed?
yum


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: 153960448 vsize: 0 resident: 153960448 share: 0 rss: 18853888 rss_rlim: 0
CPU usage: start_time: 1161863186 rtime: 0 utime: 1692 stime: 0 cutime:421 cstime: 0 timeout: 1271 it_real_value: 0 frequency: 3030

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 -1208944944 (LWP 2968)]
[New Thread -1254888560 (LWP 2972)]
(no debugging symbols found)
0x00afb402 in __kernel_vsyscall ()

+ Trace 78424

Thread 1 (Thread -1208944944 (LWP 2968))

#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 Fabio Bonelli 2006-10-26 13:06:10 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 348814 ***

Comment 2 Behdad Esfahbod 2006-11-01 23:34:14 UTC

Duping to correct bug.  Seems like 348979 was not a dupe of 348814 afterall.

*** This bug has been marked as a duplicate of 348979 ***