From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040926 Firefox/0.10 Description of problem: FC3T2 can correctly mount my USB external disk's 2 partitions(FAT32), and I can use CLI and other GUI applications to access the whole disk contents without any problem. But, Nautilus can only open the top level directory, not any further. I always got the error message 'openning xxx, you can stop this operation by clicking cancel.'. Version-Release number of selected component (if applicable): nautilus-2.8.0-1 How reproducible: Always Steps to Reproduce: 1. plug in the USB external HD 2. boot the system into GNOME 2.8 3. there are two USB disk icons on the desktop 4. double-click on one of them to open the top level directory list 5. double-click on any of the sub-directoy icons Actual Results: the sub-directory won't be opened. Message 'openning xxx, you can stop this operation by clicking cancel.' will show after a couple of seconds Expected Results: it should open a new directory window to show sub-directory content Additional info:
Can you get an strace of when this happens?
I am not an Linux expert. Can you tell me the whole command?
remove nautilus from the session (so it doesn't restart), kill it, and then run "strace -o nautilus.log -tt -f nautilus", navigate to the disk where it hangs, and attach nautilus.log here.
bug 129966 seems very similar, but on fc2 due to a kernel upgrade, so this might be kernel related.
This is exactly my problem also--I am bug 129966.
I have the strace you requested but it will not let me attached it. It says it is too big. What do you want me to do??
How big is it if you gzip it?
Created attachment 104631 [details] OK--gzipping did the trick Here you go.
Do you get any messages in /var/log/messages when this happens? Also, what sort of filenames are in the directory, and how does the mount command line for the filesystem in /etc/fstab?
Need to merge this bug with 129966.
*** This bug has been marked as a duplicate of 129966 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.