Bug 366360 – crash in CD/DVD Creator: ? Opening a directory in...

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 366360 - crash in CD/DVD Creator: ? Opening a directory in...


Summary:	crash in CD/DVD Creator: ? Opening a directory in...


Status:	RESOLVED DUPLICATE of bug 355216

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-10-28 16:00 UTC by eshuis6
Modified:	2006-10-28 16:05 UTC

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

Description eshuis6 2006-10-28 16:00:40 UTC

What were you doing when the application crashed?
? Opening a directory in Nautilus.


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: 519340032 vsize: 519340032 resident: 37875712 share: 23932928 rss: 37875712 rss_rlim: -1
CPU usage: start_time: 1162048168 rtime: 24488 utime: 2300 stime: 22188 cutime:194 cstime: 33 timeout: 0 it_real_value: 0 frequency: 100

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

(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 46912697202848 (LWP 2792)]
(no debugging symbols found)
0x00002aaab0e7d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 79333

Thread 1 (Thread 46912697202848 (LWP 2792))

#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 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 g_logv
from /lib64/libglib-2.0.so.0
#6 g_log
from /lib64/libglib-2.0.so.0
#7 g_assert_warning
from /lib64/libglib-2.0.so.0
#8 nautilus_file_get_uri
#9 nautilus_icon_container_request_update_all
#10 nautilus_icon_container_request_update_all
#11 fm_directory_view_bump_zoom_level
#12 fm_directory_view_bump_zoom_level
#13 fm_directory_view_bump_zoom_level
#14 fm_directory_view_bump_zoom_level
#15 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#16 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#17 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#18 g_signal_emit
from /lib64/libgobject-2.0.so.0
#19 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#20 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#22 g_signal_emit
from /lib64/libgobject-2.0.so.0
#23 gtk_icon_info_get_type
from /usr/lib64/libgtk-x11-2.0.so.0
#24 gtk_icon_theme_rescan_if_needed
from /usr/lib64/libgtk-x11-2.0.so.0
#25 gtk_icon_theme_rescan_if_needed
from /usr/lib64/libgtk-x11-2.0.so.0
#26 gtk_icon_theme_has_icon
from /usr/lib64/libgtk-x11-2.0.so.0
#27 gnome_icon_lookup
from /usr/lib64/libgnomeui-2.so.0
#28 nautilus_icon_container_request_update_all
#29 nautilus_file_ref
#30 nautilus_file_ref
#31 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#32 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#33 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#34 g_signal_emit
from /lib64/libgobject-2.0.so.0
#35 fm_directory_view_bump_zoom_level
#36 g_source_get_current_time
from /lib64/libglib-2.0.so.0
#37 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#38 g_main_context_check
from /lib64/libglib-2.0.so.0
#39 g_main_loop_run
from /lib64/libglib-2.0.so.0
#40 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#41 POA_Nautilus_MetafileMonitor__init
#42 __libc_start_main
from /lib64/libc.so.6
#43 g_cclosure_marshal_VOID__ENUM
#44 ??
#45 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Rob Bradford 2006-10-28 16:05: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 355216 ***