Use the following statements in Terminal.
sudo vi /etc/auto_master
In this file comment out /net with # (#/net .....)
sudo automount -vc
Confirmed here too both for Preview.app Open file sluggishness and Finder window population. Thanks Snaggletooh_DE!
Couple of notes:
(1) Some folks may be more comfortable using a GUI editor like TextWrangler instead of vi
a) in the Finder use the GO menu and select Go to Folder
b) type '/etc' ( without single quotes ) in the Go to folder dialog box and press the Go button
c) Right ( Control ) click the auto_master file in the resulting Finder window. Select "Open with...." and use TextWrangler ( your choice )
d) Comment out the line by inserting a '#' ( pound sign ) as noted in Snaggletooth_DE's instructions
e) Save the file ( probably need to authenticate with your admin password )
f) Do the 'sudo automount -vc' per Snaggletooth_DE's instructions. Will need to authenticate again.
(2) Notice Snaggletooth_DE described this as a "workaround" because it bypasses an Apple bug. Presumably most people have not changed their auto_master file and it worked fine in Mountain Lion and prior. In other words: If you haven't done so already, please continue to submit feedback and bug reports to Apple for this issue
Kudos to Snaggletooth_DE for figuring out code is trying to look at network ( NFS ) volumes that maybe don't exist.
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!
This bug was like some sort of Chinese water torture. The irritation just built and built. I thought I was going to go nuts. I spend so much time working with photographic and audio files. All the things I have tried including the last resort in-place reinstall of OS X 10.9 when I had given up and as requested by the so-called experts in AppleCare support which led to more problems that I had to fix and still had this one annoying Open/Save/Export/Import dialog issue. I had assumed it had something to do with the messages I was seeing written for "com.apple.appkit.xpc.openAndSavePanelService" and was at a complete loss and had decided to give up and hope, wish, wait for Apple to release a fix in a one-off.
Now, more than one month later, your workaround worked and you are my hero today, Snaggletooth_DE
P.S. This type of issue is the very reason I have always waited until the first update (10.x.1) was available and Mavericks has taught me how wise such waiting was.
This bug was like some sort of Chinese water torture.
...had decided to give up and hope, wish, wait for Apple to release a fix in a one-off.
I provided my feedback and reported it via the about one week into using Mavericks (I had hoped it was a caching issue, or, if a bug, something that had been around and a quick fix would be released for) after 10.9 went GA, and then the AppleCare rep said they would also report it to their developers (right...). But, like most other incredibly quirky foundational issues that I may actually call them for help with, it's "news to them" and they almost always have never heard of what I am asking them for help with (or so they claim)... So, I agree, the more feedback the better. I hope your reference to NDA means you know something good is coming, but, I will not press you for anymore info
after 10.9 went GA,
and then the AppleCare rep said they would also report it to their developers (right...).
Haven't seen 'GA' since I left the mainframe developer business. Thanks for memory.
In my experience many developement fixes were driven by the quantity of issues reported to the frontline support folks. That might happen with AppleCare if they are opening support tickets that get tracked. There is usually someone watching the support metrics.
I would be very grateful if someone could go into slightly more detail about this workaround. I'm not scared of going into Terminal, but I'm not familiar with "commenting out" items, or what buttons to press in order to facilitate these commands. Any additional explainations are appreciated tremendously!
what are the steps between commenting out and sudo automount -vc?
My post in this thread on Nov. 20th shows steps using TextWrangler ( a text editor ). Is this enough detail?
At a high-level the steps are:
(1) Launch a text editor like TextWrangler and edit the file and make the change noted
(2) Save the file from within the text editor
(3) Exit the text editor ( not required but you don't need it after the edit is complete )
(4) Launch Terminal.app
(5) enter the 'sudo automount -vc' command in Terminal
(6) exit Terminal app
As others have already noted, be careful not to change the file type ( TextWrangler won't ). Making a copy of the file before you make changes is wise but probably overkill since this simple change can be easily backed out.
Here is what I suggest:
- Open Terminal and invoke: cd /etc
- To make sure you have a backup of an assumed known-good file, invoke: sudo cp auto_master auto_master.backup (Enter your admin password when prompted.)
- You can confirm that both files exist by invoking: ls auto_master*. The "cp" command just copies one file to another, so this step is duplicating the existing auto_master file.
- Now that you are already in /etc, simply invoke: sudo nano auto_master
- Use your arrow keys to place the cursor in front of the line beginning with "/net" and then type "#" (without the quotes).
- Press Control-O (Control -- not Command -- and the "Oh" keys at the same time) and then press Enter/Return to confirm and write out to auto_master.
- Control-X to to exit nano.
- From Terminal you can confirm the change by invoking: more auto_master (You can "more auto_master.backup" to see what the file used to look like - the only difference should be that the /net entry is commented out with the #.)
- Invoke: sudo automount -vc
You're done. Exit the Terminal and you should be good to go. This workaround works for me. If Apple releases a fix in a future update for 10.9, be sure to revert the change before applying the proper fix from Apple.
Update: Using GUI file editors is easy, but so is using an editor like nano (beats vi when the option exists). I am not contradicting Brilor's instructions, but providing as detailed a description as possible to work with CLI tools as I think if one is going to implement a workaround like this then one should feel comfortable with the command line and its tools.