Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just installed VMware Workstation 8.0.3 on ubuntu 12.04. Everytime it starts up it says that vmware needs ~/.vmware to save preferences and that it is unable to create ~/.vmware.

But ~/.vmware is already a directory. How do I get this resolved?

share|improve this question
This might be a permissions problem, caused by having run VMware as root (but there are other possible causes too). Please edit your question to add the output of these three commands (run them in the Terminal, which you can open by pressing Ctrl+Alt+T): [1] ls -ldh ~/.vmware [2] ls -lRh ~/.vmware [3] df -h Please also add the complete and exact text of the error messages, as well as the the text you get in the Terminal when you try to start vmware there (when it's not already running). – Eliah Kagan Jun 5 '12 at 3:26
This helped on Ubuntu 14.04 64bit and Workstation 10.02: sudo chown -R username:username ~/.vmware Thanks for helping this out ldgriffin and daviderault Regards – pecuna May 11 '14 at 7:07

You should never run as root unless you are explicitly trying to modify your system. VMWare Workstation does not need root access to simply run a guest machine. Likely your permission were changed to root owning your ~/.vmware folder during install. You just need to change the ownership back to your user.

sudo chown -R $USER:$USER ~/.vmware

This will set the owner back to you and your group.

share|improve this answer

I had the same problem with VMWare Player 6.0 in Ubuntu 13.10

I solved it by using:

chown -R $USER:$USER ~/.vmware
share|improve this answer

Try running as root, it always helps get things done.

share|improve this answer
Running as root will not help an issue of writing to one's home folder. Read the error carefully, please. – hexafraction Aug 16 '12 at 19:05
It might, since the problem is that part of the user's home folder has come to be owned by root. It's still a bad idea though--instead, ownership should be retaken on the affected files. – Eliah Kagan Aug 17 '12 at 1:26

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.