You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My problem is not solved in the Troubleshooting docs
Anaconda default channels
I do NOT use the Anaconda default channels (pkgs/* etc.)
How did you install Mamba?
I installed Miniconda originally then replaced all packages in my base environment with conda-forge versions and installed mamba from conda-forge (I only use Miniconda because I want the Powershell launcher on Windows which I can't get with Miniforge).
Search tried in issue tracker
Yes I looked
Latest version of Mamba
My problem is not solved with the latest version
Tried in Conda?
I have this problem with Conda as well, without using Mamba
Describe your issue
Mamba was working fine for me, I updated my base environment and started getting DLL errors after updating fmt for all mamba commands:
Traceback (most recent call last):
File "C:\Users\Owen\miniconda3\Scripts\mamba-script.py", line 6, in <module>
from mamba.mamba import main
File "C:\Users\Owen\miniconda3\Lib\site-packages\mamba\mamba.py", line 44, in <module>
import libmambapy as api
File "C:\Users\Owen\miniconda3\Lib\site-packages\libmambapy\__init__.py", line 7, in <module>
raise e
File "C:\Users\Owen\miniconda3\Lib\site-packages\libmambapy\__init__.py", line 4, in <module>
from libmambapy.bindings import * # noqa: F401,F403
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ImportError: DLL load failed while importing bindings: The specified procedure could not be found.
These were the packages I updated in my base environment before mamba broke... but I determined fmt was the issue:
I updated another Windows computer that didn't have grayskull installed (just setuptools and fmt) and ran into exactly the same problem. This dll problem has also partially broken conda (I can't downgrade fmt with conda using the default libmamba solver). I get these errors:
conda install fmt=10.1.1 -c conda-forge
Error while loading conda entry point: conda-libmamba-solver (DLL load failed while importing bindings: The specified procedure could not be found.)
Retrieving notices: ...working... done
CondaValueError: You have chosen a non-default solver backend (libmamba) but it was not recognized. Choose one of: classic
I was able to downgrade fmt with conda (after switching back to the classis solver):
Once fmt was downgraded mamba appears to be working again. I originally suspected setuptools was the issue but I downgraded that first and it didn't fix the problem.
mamba info / micromamba info
I can't run this as mamba is now broken, I'm using mamba version 1.5.6
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
I installed Miniconda originally then replaced all packages in my base environment with conda-forge versions and installed mamba from conda-forge (I only use Miniconda because I want the Powershell launcher on Windows which I can't get with Miniforge).
Search tried in issue tracker
Yes I looked
Latest version of Mamba
Tried in Conda?
I have this problem with Conda as well, without using Mamba
Describe your issue
Mamba was working fine for me, I updated my base environment and started getting DLL errors after updating fmt for all mamba commands:
These were the packages I updated in my base environment before mamba broke... but I determined fmt was the issue:
I updated another Windows computer that didn't have grayskull installed (just setuptools and fmt) and ran into exactly the same problem. This dll problem has also partially broken conda (I can't downgrade fmt with conda using the default libmamba solver). I get these errors:
I was able to downgrade fmt with conda (after switching back to the classis solver):
Once fmt was downgraded mamba appears to be working again. I originally suspected setuptools was the issue but I downgraded that first and it didn't fix the problem.
mamba info / micromamba info
I can't run this as mamba is now broken, I'm using mamba version 1.5.6
Logs
No response
environment.yml
~/.condarc
The text was updated successfully, but these errors were encountered: