Bug 370159 – crash in CD/DVD Creator: updating 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 370159 - crash in CD/DVD Creator: updating yum


Summary:	crash in CD/DVD Creator: updating yum


Status:	RESOLVED DUPLICATE of bug 351713

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-03 19:25 UTC by peter-s
Modified:	2006-11-03 19:36 UTC

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

Description peter-s 2006-11-03 19:25:01 UTC

What were you doing when the application crashed?
updating 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: 74637312 vsize: 0 resident: 74637312 share: 0 rss: 14213120 rss_rlim: 0
CPU usage: start_time: 1162568901 rtime: 0 utime: 3830 stime: 0 cutime:3765 cstime: 0 timeout: 65 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/nautilus'

(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 -1208317184 (LWP 8561)]
(no debugging symbols found)
0x0027c402 in __kernel_vsyscall ()

+ Trace 82470

Thread 1 (Thread -1208317184 (LWP 8561))

#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 nautilus_directory_async_state_changed
#5 nautilus_file_get_uri
#6 nautilus_file_get_uri
#7 nautilus_file_has_volume
#8 nautilus_icon_container_request_update_all
#9 fm_directory_view_bump_zoom_level
#10 nautilus_file_ref
#11 nautilus_icon_container_request_update_all
#12 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#13 g_closure_invoke
from /lib/libgobject-2.0.so.0
#14 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#16 g_signal_emit
from /lib/libgobject-2.0.so.0
#17 nautilus_icon_container_request_update_all
#18 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /lib/libgobject-2.0.so.0
#20 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#22 g_signal_emit
from /lib/libgobject-2.0.so.0
#23 gtk_icon_info_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_icon_theme_rescan_if_needed
from /usr/lib/libgtk-x11-2.0.so.0
#25 gtk_icon_theme_rescan_if_needed
from /usr/lib/libgtk-x11-2.0.so.0
#26 gtk_icon_theme_rescan_if_needed
from /usr/lib/libgtk-x11-2.0.so.0
#27 gtk_window_new
from /usr/lib/libgtk-x11-2.0.so.0
#28 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#29 g_value_set_static_boxed
from /lib/libgobject-2.0.so.0
#30 g_closure_invoke
from /lib/libgobject-2.0.so.0
#31 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#33 g_signal_emit
from /lib/libgobject-2.0.so.0
#34 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#36 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#37 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#38 g_main_context_check
from /lib/libglib-2.0.so.0
#39 g_main_loop_run
from /lib/libglib-2.0.so.0
#40 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#41 POA_Nautilus_MetafileMonitor__init
#42 __libc_start_main
from /lib/libc.so.6
#43 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-11-03 19:36:58 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 351713 ***