GNOME Bugzilla – Bug 390371
crash in CD/DVD Creator: #fdisk -1
Last modified: 2006-12-28 19:57:28 UTC
What were you doing when the application crashed? #fdisk -1 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.18-1.2868.fc6 #1 SMP Fri Dec 15 17:29:48 EST 2006 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors --------------------- (nautilus:4480): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:4480): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed (nautilus:4480): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:4480): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:4480): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:4480): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:4480): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed ** (bug-buddy:4493): WARNING **: 无法为 打开文件夹 载入图标 -------------------------------------------------- Memory status: size: 484945920 vsize: 484945920 resident: 24276992 share: 14352384 rss: 24276992 rss_rlim: -1 CPU usage: start_time: 1167317828 rtime: 103 utime: 95 stime: 8 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 46912496363456 (LWP 4480)] (no debugging symbols found) 0x000000398600d96f in waitpid () from /lib64/libpthread.so.0
+ Trace 97557
Thread 1 (Thread 46912496363456 (LWP 4480))
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 363856 ***