GNOME Bugzilla – Bug 383142
crash in Computer: changing the selinux dro...
Last modified: 2006-12-06 20:43:16 UTC
Version: 2.16.2 What were you doing when the application crashed? changing the selinux dropdown from the permissions pane of the properties window so I can delete the file from the trash can 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.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: Disabled ----------- .xsession-errors --------------------- ** Message: Hit unexpected error "Directory not empty" while doing a file operation. ** Message: Hit unexpected error "Directory not empty" while doing a file operation. ** Message: Hit unexpected error "Directory not empty" while doing a file operation. Window manager warning: Invalid WM_TRANSIENT_FOR window 0x0 specified for 0x24002b0 (). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x0 specified for 0x24003f6 (). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x0 specified for 0x2400538 (). ** Message: Hit unexpected error "Directory not empty" while doing a file operation. ** Message: Hit unexpected error "Directory not empty" while doing a file operation. ** Message: Hit unexpected error "Directory not empty" while doing a file operation. ** (bug-buddy:4580): WARNING **: Couldn't load icon for Open Folder Initializing nautilus-open-terminal extension Initializing nautilus-search-tool extension ** (bug-buddy:4633): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 93356032 vsize: 0 resident: 93356032 share: 0 rss: 26796032 rss_rlim: 0 CPU usage: start_time: 1165436969 rtime: 0 utime: 446 stime: 0 cutime:416 cstime: 0 timeout: 30 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 -1208452352 (LWP 4602)] (no debugging symbols found) 0x003ce402 in __kernel_vsyscall ()
+ Trace 92138
Thread 1 (Thread -1208452352 (LWP 4602))
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 362302 ***