conda init gives me "no action taken"

Question

I'm getting this while installing anaconda on ubuntu 19.04 Im getting this while installing anaconda on ubuntu 19.04

make sure you have root permission. type in terminal command su - and it will ask you root password and then try to install. — JackyChan, May 14 '19 at 12:46
@JackyChan: anaconda does not need root priviledges when installed in the home directory of a user. — Thomas, May 14 '19 at 13:32
Did you upgrade anaconda or just did a fresh install? Maybe nothing has to be done by conda init? It looks like the conda environment is set up already. Does conda activate <environment> work? — Thomas, May 14 '19 at 13:35
I think you done everything. Then just run the command anaconda-navigator in terminal — Ganesh Kanna, Sep 07 '19 at 14:53
Please copy and paste logs in text (or type in), do not post an image for text output. — 0xc0de, Nov 20 '19 at 12:52

score 13 · Answer 1 · answered Nov 20 '19 at 10:52

13

While this does not try to fix this problem, rather helps as a workaround when I want to activate an env.

$ source ~/anaconda3/bin/activate <env_name>

answered Nov 20 '19 at 10:52

0xc0de

255

score 7 · Answer 2 · edited May 10 '20 at 06:06

I had the same problem. Previously I had anaconda 2 but I removed to install anaconda 3. After installing anaconda 3 and using conda init I got the same error message, as I solved it. Enter your .bashrc:

gedit ~/.bashrc

Identify the following lines in the .bashrc file and delete them:

# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup = "$ ('/ home / spidey / anaconda3 / bin / conda' 'shell.bash' 
'hook' 2> / dev / null)"
if [$? -eq 0]; then
    eval "$ __ conda_setup"
else
    if [-f "/home/spidey/anaconda3/etc/profile.d/conda.sh"]; then
        . "/home/spidey/anaconda3/etc/profile.d/conda.sh"
    else
        export PATH = "/ home / spidey / anaconda3 / bin: $ PATH"
    fi
fi
unset __conda_setup
# <<< conda initialize <<<

Explanation:
Since previously you already had an anaconda installation, the conda init command did not modify anything because it detected that you had already made changes to the .bashrc file.

score 3 · Answer 3 · answered Nov 20 '19 at 09:03

3

Try By Using anaconda-navigator:

activate conda:

$ source ~/anaconda3/bin/activate root

Launch conda:

$ anaconda-navigator

If you want to launch JupyterNotebook simply run

jupyter notebook

answered Nov 20 '19 at 09:03

Dinesh Kc

31

This works for me – Marie Jan 23 '20 at 19:42

score 2 · Answer 4 · answered Nov 05 '20 at 12:48

2

I found the solution

/opt/conda/bin/conda init zsh

as it states here (from /opt/conda/bin/conda init -h )

positional arguments: shells One or more shells to be initialized. If not given, the default value is 'bash' on unix and 'cmd.exe' on Windows. Use the '--all' flag to initialize all shells. Currently compatible shells are {bash, fish, powershell, tcsh, xonsh, zsh}

This is weird because I did not have this problem before while setting up another server. But anyway it is clear that you need to specify the shell (which is zsh here), otherwise conda will pick up bash as default shell.

answered Nov 05 '20 at 12:48

Long

123

Indeed: conda init zsh followed by source ~/.zshrc (or any other shell) – bathyscapher Nov 27 '24 at 13:23
normally I always log out then log in, but source should work too. Sometimes my shell hangs when sourcing so I don't do it often. – Long Dec 02 '24 at 06:00
1

Maybe it's time to clean up the sourced file then? ;) – bathyscapher Dec 02 '24 at 07:51
1

it happened once or twice in the past on some test servers and at that time I didn't look for the reason. I think you're right about the mess I created in ~/.zshrc. Just tried sourcing on my current server, it ran well ^_^. Thanks. – Long Dec 02 '24 at 07:57

score 2 · Answer 5 · answered Mar 25 '22 at 06:11

2

source ~/.bashrc or source ~/.bash_profile should work

answered Mar 25 '22 at 06:11

muTheTechie

121
2

yogogoba · Answer 6 · 2020-04-21T15:43:35.837

0

As far as I understand this, conda init [shell] is used to initiate a specific shell utilized when executing command-line conda commands. Not specifying one will default it to bash, which I'm guessing is what you already use here—since this is the output.

More information can be found by using the [-h] flag:

$ conda init -h

edited Apr 21 '20 at 15:43

answered Apr 21 '20 at 15:12

yogogoba

1
3

score 0 · Answer 7 · edited Jun 13 '20 at 15:59

0

Use this instead:

conda activate
jupyter notebook

edited Jun 13 '20 at 15:59

Eliah Kagan

119,820

answered Jun 13 '20 at 13:12

amirsalah

1

conda init gives me "no action taken"

7 Answers7