GNOME Bugzilla – Bug 418106
crash in CD/DVD Creator:
Last modified: 2007-03-17 02:58:55 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.fc6 #1 SMP Sat Feb 10 15:51:47 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 89575424 vsize: 0 resident: 89575424 share: 0 rss: 25526272 rss_rlim: 0 CPU usage: start_time: 1173324230 rtime: 0 utime: 383 stime: 0 cutime:333 cstime: 0 timeout: 50 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 -1208940848 (LWP 15567)] (no debugging symbols found) 0x00899402 in __kernel_vsyscall ()
+ Trace 118467
Thread 1 (Thread -1208940848 (LWP 15567))
----------- .xsession-errors (11 sec old) --------------------- (nautilus:15567): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:15567): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed (nautilus:15567): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:15567): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:15567): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:15567): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:15567): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed ** (bug-buddy:15612): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
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 ***