Bug 438594 – crash in CD/DVD Creator: ????? ??? ??????? ?? ???...

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 438594 - crash in CD/DVD Creator: ????? ??? ??????? ?? ???...


Summary:	crash in CD/DVD Creator: ????? ??? ??????? ?? ???...


Status:	RESOLVED DUPLICATE of bug 362302

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:	2007-05-15 13:08 UTC by zealczg
Modified:	2007-05-15 13:46 UTC

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

Description zealczg 2007-05-15 13:08:35 UTC

What were you doing when the application crashed?
在计算机下 创建了 文件夹，删除也 删除 不了，多 弄几次就出 错误 了


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: 532226048 vsize: 532226048 resident: 38559744 share: 25071616 rss: 38559744 rss_rlim: -1
CPU usage: start_time: 1179234142 rtime: 701 utime: 621 stime: 80 cutime:0 cstime: 0 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 3102)]
(no debugging symbols found)
0x00002aaab0e7d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 134280

Thread 1 (Thread 46912697202848 (LWP 3102))

#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 strcmp
from /lib64/libc.so.6
#4 nautilus_file_ref
#5 fm_directory_view_bump_zoom_level
#6 fm_directory_view_bump_zoom_level
#7 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#8 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit
from /lib64/libgobject-2.0.so.0
#11 gtk_combo_new
from /usr/lib64/libgtk-x11-2.0.so.0
#12 gtk_combo_box_set_active_iter
from /usr/lib64/libgtk-x11-2.0.so.0
#13 gtk_combo_box_set_active_iter
from /usr/lib64/libgtk-x11-2.0.so.0
#14 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#15 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#17 g_signal_emit
from /lib64/libgobject-2.0.so.0
#18 gtk_widget_activate
from /usr/lib64/libgtk-x11-2.0.so.0
#19 gtk_menu_shell_activate_item
from /usr/lib64/libgtk-x11-2.0.so.0
#20 gtk_menu_shell_append
from /usr/lib64/libgtk-x11-2.0.so.0
#21 gtk_marshal_BOOLEAN__VOID
from /usr/lib64/libgtk-x11-2.0.so.0
#22 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#23 g_signal_override_class_closure
from /lib64/libgobject-2.0.so.0
#24 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#25 g_signal_emit
from /lib64/libgobject-2.0.so.0
#26 gtk_widget_get_default_style
from /usr/lib64/libgtk-x11-2.0.so.0
#27 gtk_propagate_event
from /usr/lib64/libgtk-x11-2.0.so.0
#28 gtk_main_do_event
from /usr/lib64/libgtk-x11-2.0.so.0
#29 gdk_add_client_message_filter
from /usr/lib64/libgdk-x11-2.0.so.0
#30 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#31 g_main_context_check
from /lib64/libglib-2.0.so.0
#32 g_main_loop_run
from /lib64/libglib-2.0.so.0
#33 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#34 POA_Nautilus_MetafileMonitor__init
#35 __libc_start_main
from /lib64/libc.so.6
#36 g_cclosure_marshal_VOID__ENUM
#37 ??
#38 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 palfrey 2007-05-15 13:46:40 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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