GNOME Bugzilla – Bug 398108
crash in Computer: Changing the SElinux Con...
Last modified: 2007-01-19 00:12:45 UTC
Version: 2.16.2 What were you doing when the application crashed? Changing the SElinux Context settings from 'file_t' to 'user' a crash resulted 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.2869.fc6 #1 SMP Wed Dec 20 14:51:19 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- package is installed and that the service is running. Initializing nautilus-image-converter extension Initializing nautilus-search-tool extension Initializing nautilus-open-terminal extension Initializing nautilus-flac-converter extension ** (nautilus:19105): CRITICAL **: nautilus_file_get_internal: assertion `uri != NULL' failed ** (nautilus:19105): WARNING **: Hit unhandled case 24 (Operation not permitted) in fm_report_error_setting_permissions ** (nautilus:19105): WARNING **: Hit unhandled case 24 (Operation not permitted) in fm_report_error_setting_permissions ** (nautilus:19105): WARNING **: Hit unhandled case 24 (Operation not permitted) in fm_report_error_setting_permissions ** (bug-buddy:19260): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 126582784 vsize: 0 resident: 126582784 share: 0 rss: 25862144 rss_rlim: 0 CPU usage: start_time: 1169147025 rtime: 0 utime: 163 stime: 0 cutime:146 cstime: 0 timeout: 17 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 -1208669440 (LWP 19105)] (no debugging symbols found) 0x003a7402 in __kernel_vsyscall ()
+ Trace 103316
Thread 1 (Thread -1208669440 (LWP 19105))
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 362302 ***