Broken Conda installation

My conda installation is broken. I would really appreciate if someone has an idea how to get my conda up and running again.
Problem: I cannot install new packages or create environments.
I always get the error below.

$ conda create -n da python
Collecting package metadata (repodata.json): done
Solving environment: | WARNING conda.resolve:_get_sat_solver_cls(57): Could not run SAT solver through interface 'pycosat'.
failed

CondaDependencyError: Cannot run solver. No functioning SAT implementations available.

When I run conda info I get this info:

  conda version : 4.11.0
    conda-build version : not installed
         python version : 3.7.12.final.0
       virtual packages : __linux=5.10.102.1=0
                          __glibc=2.31=0
                          __unix=0=0
                          __archspec=1=x86_64
       base environment : /home/eero_ds/miniforge-pypy3  (writable)
      conda av data dir : /home/eero_ds/miniforge-pypy3/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/intel/linux-64
                          https://conda.anaconda.org/intel/noarch
                          https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /home/eero_ds/miniforge-pypy3/pkgs
                          /home/eero_ds/.conda/pkgs
       envs directories : /home/eero_ds/miniforge-pypy3/envs
                          /home/eero_ds/.conda/envs
               platform : linux-64
             user-agent : conda/4.11.0 requests/2.25.1 PyPy/3.7.12 Linux/5.10.102.1-microsoft-standard-WSL2 ubuntu/20.04.4 glibc/2.31
                UID:GID : 1000:1000
             netrc file : None
           offline mode : False

The obvious fix would be to reinstall, which I have done without errors. I downloaded a new version of anaconda from anaconda.org and run

bash Anaconda3-2022.05-Linux-x86_64.sh -u

I have checked out Stackoverflow and Google without finding anything that seems relevant enough to try.

Sincerely,
Eero

1 Like

hello.

Sounds like a lot of trouble. First of all, I would like to give you some simple advice.

During updates and installations, when Solver is giving errors, it is very likely that there is a conflict between the installed packages.

One way to change this situation is to create an environment with different versions of python.

For example, set the python version to 3.7 and create an environment for 3.7. Execute the following command on the shell.

(base) $ conda create --name py37 python = 3.7

The created environment is activated by the conda activate environment name.

(base) $ conda activate py37
(py37) $

In the environment created in this way
(py37)$ conda info

You can get information about the created environment by executing.

again,
(py37)$ conda config --show
Then, Display all configuration values ​​as calculated and compiled.

In some cases, using such information as a reference, removing the conflicting package once and updating it with a new one will solve the problem.

In particular, it may conflict with python on your system. In that case, it is important to have Anaconda available in user mode instead of removing Python from the system.

What I would like you to check is
user config file: /home//.condarc
populated config files: /home/
/.condarc
Does it exist? How is it?

@Eero_Olli Thank you for posting your issue! That is a very odd error that it says that there is no functioning SAT implementation available. Based on the results of conda info, it looks like you originally installed miniforge? Also, I don’t see any populated conda config files in those results either.

After you installed Anaconda, what is the output of conda info? You may need to activate the new installation or make it your default. Have you taken a look at your bash shell configuration file?