Mavericks and slow Finder

Last weekend I upgraded my MBP to Mavericks. I have been waiting with the upgrade because I didn’t want to have problem with my computer so I figured I’ll wait for some bugfixes before upgrading. So last weekend I decided to take the jump and upgrade. The first thing I discovered was that HyperSwitch was not working as it should and I still have not found a solution to the problem. The next problem was that Finder was incredibly slow when showing the content in folders. Today I was googling for a solution and I encountered a solution by Snaggletooth_DE,

The solution is to edit the auto_master file.

  1. Open up a Terminal window
  2. Open up the file auto_master
     $ sudo nano /etc/auto_master
  3. Comment out the row “/net  -hosts -nobrowse,hidefromfinder,nosuid”
     #/net                    -hosts          -nobrowse,hidefromfinder,nosuid
  4. Save the file with Ctrl+X
  5. Now restart the computer.
     $ sudo restart

After I have done the changes my Finder was as responsive as it used to be. I decided to test and see if I could reproduce the problem by uncomment the same row. So I did that and restarted. The funny thing now was that Finder was still responsive so I decided to go with that and close the case.

“Eclipse” is damaged and can’t be opened.

Yesterday I downloaded the latest Eclipse named Kepler to my Mac. I unzipped the package as usual and tried to launch it by clicking on the Eclipse file. I received the following error message:


After a quick search on the internet I found the solution in a bug report at Eclipse Bugs . It is the OS X GateKeeper that thinks that the file is corrupt and should be moved to trash. However, the problem is easy the solve. Just follow the following steps.

  1. Open up a shell
  2. Cd yourself into the eclipse directory.
  3. Check the attributes of the directory
    $ xattr
  4. Remove the ‘’ attribute.
    $ xattr -d

Now you should be able to launch Eclipse.

Happy coding

No sound in OS X when playing YouTube videos in Chrome

It have happened a couple of times that I suddenly don’t have any sound from my speakers when watching YouTube videos in Chrome. I don’t know how and when this happens but it is easy to fix. Just open a terminal and run “sudo killall coreaudiod”. I probably should investigate why this happens but I will do that on a rainy day.

$ sudo killall coreaudiod

That’s it.