Bug 417346 – 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 417346 - crash in CD/DVD Creator: 强行关机


Summary:	crash in CD/DVD Creator: 强行关机


Status:	RESOLVED DUPLICATE of bug 389087

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-03-12 04:55 UTC by fuxiang20004
Modified:	2007-03-13 19:45 UTC

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

Description fuxiang20004 2007-03-12 04:55:10 UTC

What were you doing when the application crashed?
强行关机			


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.19-1.2911.6.5.fc6xen #1 SMP Sun Mar 4 16:59:41 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 147943424 vsize: 0 resident: 147943424 share: 0 rss: 28073984 rss_rlim: 0
CPU usage: start_time: 1173675235 rtime: 0 utime: 96 stime: 0 cutime:75 cstime: 0 timeout: 21 it_real_value: 0 frequency: 70

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208444160 (LWP 3610)]
(no debugging symbols found)
0x00176402 in __kernel_vsyscall ()

+ Trace 117907

Thread 1 (Thread -1208444160 (LWP 3610))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/nosegneg/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gtk_hsv_new
from /usr/lib/libgtk-x11-2.0.so.0
#5 gtk_hsv_new
from /usr/lib/libgtk-x11-2.0.so.0
#6 gtk_icon_info_get_type
from /usr/lib/libgtk-x11-2.0.so.0
#7 gtk_icon_theme_get_icon_sizes
from /usr/lib/libgtk-x11-2.0.so.0
#8 gtk_window_get_default_icon_list
from /usr/lib/libgtk-x11-2.0.so.0
#9 gtk_window_get_default_icon_list
from /usr/lib/libgtk-x11-2.0.so.0
#10 gtk_window_set_icon_name
from /usr/lib/libgtk-x11-2.0.so.0
#11 POA_Nautilus_MetafileMonitor__init
#12 POA_Nautilus_MetafileMonitor__init
#13 POA_Nautilus_MetafileMonitor__init
#14 nautilus_undo_transaction_unregister_object
#15 fm_directory_view_bump_zoom_level
#16 nautilus_clipboard_monitor_emit_changed
#17 nautilus_clipboard_monitor_emit_changed
#18 nautilus_directory_async_state_changed
#19 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#21 g_main_context_check
from /lib/libglib-2.0.so.0
#22 g_main_loop_run
from /lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 POA_Nautilus_MetafileMonitor__init
#25 __libc_start_main
from /lib/i686/nosegneg/libc.so.6
#26 g_cclosure_marshal_VOID__ENUM
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
You can not run beagle as root.  Beagle is designed to run from your own
user account.  If you want to create multiuser or system-wide indexes, use
the beagle-build-index tool.
You can override this setting using the beagle-config or beagle-settings tools.
** (bug-buddy:3507): WARNING **: 无法为 打开文件夹 载入图标
** (bug-buddy:3561): WARNING **: 无法为 打开文件夹 载入图标
** (bug-buddy:3597): WARNING **: 无法为 打开文件夹 载入图标
** (bug-buddy:3629): WARNING **: 无法为 打开文件夹 载入图标
** (bug-buddy:3627): WARNING **: 无法为 打开文件夹 载入图标
--------------------------------------------------

Comment 1 André Klapper 2007-03-13 19:45:27 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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