GNOME Bugzilla – Bug 458718
crash in CD/DVD Creator:
Last modified: 2007-07-28 23:09:36 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.fc6 #1 SMP Sun Mar 4 16:41:13 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Permissive Accessibility: Disabled Memory status: size: 85807104 vsize: 0 resident: 85807104 share: 0 rss: 24190976 rss_rlim: 0 CPU usage: start_time: 1184951473 rtime: 0 utime: 269 stime: 0 cutime:249 cstime: 0 timeout: 20 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 -1209099520 (LWP 3464)] (no debugging symbols found) 0x00d9b402 in __kernel_vsyscall ()
+ Trace 149401
Thread 1 (Thread -1209099520 (LWP 3464))
----------- .xsession-errors --------------------- calendar-61141-69058e5435eed3686148f48d663fdce2 has recurrences mapping method init - connect: Permission denied (nautilus:3464): libgnomevfs-WARNING **: module '/usr/lib/gnome-vfs-2.0/modules/libmapping.so' returned a NULL handle mapping method init - connect: Permission denied (nautilus:3464): libgnomevfs-WARNING **: module '/usr/lib/gnome-vfs-2.0/modules/libmapping.so' returned a NULL handle mapping method init - connect: Permission denied (nautilus:3464): libgnomevfs-WARNING **: module '/usr/lib/gnome-vfs-2.0/modules/libmapping.so' returned a NULL handle mapping method init - connect: Permission denied (nautilus:3464): libgnomevfs-WARNING **: module '/usr/lib/gnome-vfs-2.0/modules/libmapping.so' returned a NULL handle ** (bug-buddy:4099): 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 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 360543 ***