Hi,
I'm running Redhat 9 with kernel-2.4.20-31.9.
Whenever I try to open Nautilus (Nautilus-2.2.1-5), it hangs at my home directory sucking up 100 % cpu. The Nautilus window is open, but I can't see files or directories and the icon in the top right corner goes round and round and round. When I shut it down, it opens right back up again, hanging. When I log out of GNOME, it takes 2-3 minutes to shut properly. If I open Nautilus on a different location (eg one of my FAT partitions), it's fine......until I travel back to my home directory, then it hangs again.
This problem seemed to happen shortly after a power cut.
I get this report after running $ gconf-sanity-check-1

Please contact your system administrator to resolve the following problem:
Failed to get a file lock: Failed to lock '/home/dbutler/.gconfd/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured, or a hard NFS client crash caused a stale lock (Resource temporarily unavailable) - run gconf-sanity-check-1 for possible diagnosis, see website* for more information

I've been to the website* (The Linuxquestions antispamming program won't let me post the full URL - gnome.org/projects/gconf/), but to be honest, it's a bit above me. I've been using Linux for 2 weeks and don't want to accidentally hose anything. If this is a problem with stale locks, is there an easy way to remove them? BTW, I don't run NFS or nfslock, so I'm not sure of the accuracy of the reported problem. Could it be something else?

I'd appreciate any help - my residual sanity is at stake

Cheers

Dave

Even on fast machines I've found that Nautilus tends to suck. To get better performance, you might want to consider using a more lightweight file manager, like ROX-filer.

Delete .gnome* .nautilus* .gconfd* folders in your home directory and start with new default gnome session.

Thanks for the suggestions.
Nautilus has actually stopped hanging after a lot of messing about with the folder preferences - I don't know what I did right, but it was obviously a fluke. I still get the same problem message after running $ gconf-sanity-check-1, so I think the main issue behind the problem in the first place is still there.
I want to get the problem with the stale locks sorted out before I look at a new file manager, but ROX-filer sounds good, I've been checking out the ROX web page. I'll delete the folders you suggested, chii-chan, when I get home from work (these are replaced automatically by gconf daemon in a new session, right?). I'll let you know how it goes.
Cheers!