GNOME Bugzilla – Bug 443978
crash in CD/DVD Creator: Changing "SELinux Contex...
Last modified: 2007-06-05 00:13:47 UTC
What were you doing when the application crashed? Changing "SELinux Context" (in Properties -> Permissions tab) of folder from "file_t" to "user data" (it crashes when selecting "temporary data" too). Distribution: Fedora Core release 6 (Rawhide) Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Enabled ----------- .xsession-errors (3601 sec old) --------------------- Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized Xlib: extension "SHAPE" missing on display ":0.0". Xlib: extension "SHAPE" missing on display ":0.0". ** (bug-buddy:3182): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 115650560 vsize: 0 resident: 115650560 share: 0 rss: 45727744 rss_rlim: 0 CPU usage: start_time: 1180969100 rtime: 0 utime: 229 stime: 0 cutime:211 cstime: 0 timeout: 18 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 -1209087232 (LWP 3155)] (no debugging symbols found) 0x0020c402 in __kernel_vsyscall ()
+ Trace 138147
Thread 1 (Thread -1209087232 (LWP 3155))
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 362302 ***