Bug 405117 – crash in Terminal: yum was updating in one ...

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 405117 - crash in Terminal: yum was updating in one ...


Summary:	crash in Terminal: yum was updating in one ...


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-02-06 20:38 UTC by g.sprog
Modified:	2007-02-06 20:39 UTC

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

Description g.sprog 2007-02-06 20:38:16 UTC

Version: 2.16.0

What were you doing when the application crashed?
yum was updating in one tab, nothing going on in the other tabs.


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

System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 19:28:18 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 98619392 vsize: 0 resident: 98619392 share: 0 rss: 22822912 rss_rlim: 0
CPU usage: start_time: 1170742455 rtime: 0 utime: 19543 stime: 0 cutime:17480 cstime: 0 timeout: 2063 it_real_value: 0 frequency: 9384

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 -1208420656 (LWP 14125)]
[New Thread -1218958448 (LWP 14130)]
(no debugging symbols found)
0x007f7402 in __kernel_vsyscall ()

+ Trace 108550

Thread 1 (Thread -1208420656 (LWP 14125))

#0 __kernel_vsyscall
#1 waitpid
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



----------- .xsession-errors (79826 sec old) ---------------------
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: 
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Mariano Suárez-Alvarez 2007-02-06 20:39:29 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 ***