GNOME Bugzilla – Bug 426787
crash in CD/DVD Creator: I ran
Last modified: 2007-04-10 18:14:28 UTC
What were you doing when the application crashed? I ran "##moduser" 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.20-1.2925.fc6 #1 SMP Sat Mar 10 18:20:58 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 88432640 vsize: 0 resident: 88432640 share: 0 rss: 16547840 rss_rlim: 0 CPU usage: start_time: 1175590298 rtime: 0 utime: 120 stime: 0 cutime:48 cstime: 0 timeout: 72 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 -1208116480 (LWP 2559)] (no debugging symbols found) 0x00529402 in __kernel_vsyscall ()
+ Trace 125386
Thread 1 (Thread -1208116480 (LWP 2559))
----------- .xsession-errors --------------------- (nautilus:2559): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:2559): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed (nautilus:2559): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:2559): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:2559): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:2559): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed (nautilus:2559): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed ** (bug-buddy:2697): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
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 364159 ***