I'm having some trouble installing Canopy on my Mac OS X (running 10.9.5) under my primary username. I get to the point where it asks for the location for the Canopy Environment Directory, but when I hit Continue, it crashes. I have been able to install it on the same computer, using my secondary username, but switching between the two usernames is less than ideal. Would love any suggestions. I already tried removing admin status from the secondary username to see if that changed anything, but it did not.
Thanks to anyone who has suggestions!
Any chance that this is relevant? https://support.enthought.com/entries/23707691-Canopy-GUI-requires-extra-setup-steps-when-user-s-home-path-contains-non-ASCII-characters
I actually had the same problem on my Mac. For me, I resolved it by changing the ownership of my home directory:
Open Terminal
Type in the following commands (hit enter after every line):
cd ~
cd ..
sudo chown <your_username> <your_directory>
replace <your_username> with your username, and <your_directory> with the directory in which all your personal files are stored
The last command may ask for a password. If it does, enter your password and hit Enter.
Related
I am learning Python and trying to install PIP. However, I keep reaching a password issue in the terminal. There seems to be a key symbol and does not allow me to type in my computer password. I'd appreciate any help.
The python password issue
In a terminal when inputting your password it does not echo. Double check your typing as well.
If you really cannot get sudo to work, then boot the system into single user mode (COMMAND+S) and repeat your command.
Actually I'm new to mac.
I accidentally took away all permissions on bin directory for users. Now I cannot access any commands and moreover I cannot even access the root user on my mac, sudo command also not running. It says you don't have permission.
Can anybody please tell me how do I resolve this issue?
Thanks!
I am using Mac OS X El Capitan Public Beta 2.
There is somehow a permission problem with my Desktop (and only this directory) because I can not delete any file.
The classic delete to bin does not work, even though I am prompted a window asking for my password and permission. (I am the administrator).
I also tried a few command lines like sudo rm - R *file* and it tells me that the operation is not permitted even after I enter my password.
Going without the rootless feature of El Capitan did not help either :
sudo nvram boot-args="rootless=0"
sudo reboot
Should I change the permissions of the Desktop directory? If so what are the original ones?
Thank you!
This could be caused by the "rootless" feature introduced in El Capitan... You can find more information about it here .
To disable "rootless", type this in the terminal (you'll have to reboot for the change to apply):
sudo nvram boot-args="rootless=0"
sudo reboot
After numerous try the answer was dead-easy : there is a "lock" option on files and directories in OS X and it was active for my desktop (right click -> information). Interesting is the fact that no command line could break it.
I have just set up a new Linux box and trying to install vagrant on it. The issue is that when I am running vagrant up command, I am getting the following error:
Vagrant failed to initialize at a very early stage:
The directory Vagrant will use to store local environment-specific
state is not accessible. The directory specified as the local data
directory must be both readable and writable for the user that is
running Vagrant.
Any idea how to fix this?
I think a better way is to provide your user the required permission to the directory by making the user the owner - where you want the vagrant to be booted:
$ sudo chown -R <user> <directory>
and then you will be easily able to do:
$ vagrant up
Using sudo for vagrant up is unusual as why do you want to run your virtual machine as a root user.
I met the same problem and I solved it by run the terminal with"run as administrator". It's quite easy.
Hope this can help you.
I encountered the same issue four years later and could not fix it using chmod or even #Ziya's comment under the initial question (which brought me closer to the resolution though).
In my case, I use Vagrant 2.2.6 on Windows 10, and use Cygwin as a command line interface.
For the error to disappear, I had to :
open Windows Explorer
right-click .vagrant folder in the location where I typed vagrant up
access the "Properties" menu
then, in the "Security" tab, update the authorizations for my user, granting total control
Properties window screenshot
Hope this can help someone else.
Please follow these steps:
1) install vagrant 1.7.1
2) install virtual box 4.1, 4.2, or 4.3
3) use the administrator name in the custom directory (e.g., for windows users c:\users\AdminName\myvagrant or for Mac/Linux users /home/Admin/myvagrant)
For instance: c:\users\safwan\myvagrant where safwan is the user with administrator rights/privileges.
Copy the file name Vagrantfile in the myvagrant forlder.
4) Now open DOS window as shown in the picture and follow the steps in the DOS window changing the admin name
i bought a MacBook Pro with OSX version 10.9.2 (Mavericks)
since this, (about 2 month) i did not any attention to what happens in my Terminal when i start typing some code in it (java codes for compile or something) but now i got that when i just start my terminal, this totally unknown line will appeared:
dukhat:~ MacBookpro$
necessary to say, my basic mac user was macbookpro when i bought this mac
but what is this "dukhat"?!
i googled it but there is no related information about...
thanks for advances...
Reset it using:
sudo scutil --set HostName newhostname
or
sudo hostname -s newhostname.
For anyone else ending up here. Apple has a guide for this. Make sure to create a separate Administrator account before attempting.
http://support.apple.com/en-us/HT201548
You have to log on with a second admin account and manually change the user folder /Users/OldUserName to /Users/NewUserName.
Then you go to System Preferences > Users & Groups where you unhinge the Lock-icon in the bottom-left. Thereafter you can Ctrl-click on the User that you want to change and select Advanced Options...
Then you can change the Account name to NewUserName and the Home directory to /Users/NewUserName.
This requires administrator privileges, and you might want to back up your data first.