mamba: [mamba stops working π οΈ] ImportError: DLL load failed while importing bindings: The specified module could not be found.
Main issue gist
Mamba stops working after installing geopandas (installing geopandas successfully using mamba itself).
How/what went wrong:
Trying to install geospatial, following basic steps in documentation:
- Creating new env with conda: successful. βοΈ
- Installing mamba in env using coda: installed successfully and works. βοΈ
- Installing geopandas in same env using mamba: mamba works and geopandas installed successfully. βοΈ
- Checking if mamba still works (trying to do anything): Fails. > ImportError: DLL load failed while importing bindings. β
Main error:
Happens when executing any mamba commend, demonstrated here through mamba list.
(error message is in french but itβs what the issue title says)
(geospatial) PS C:\Users\DELL> mamba list
Traceback (most recent call last):
File "C:\ProgramData\Anaconda3\envs\geospatial\Scripts\mamba-script.py", line 6, in <module>
from mamba.mamba import main
File "C:\ProgramData\Anaconda3\envs\geospatial\lib\site-packages\mamba\mamba.py", line 49, in <module>
import libmambapy as api
File "C:\ProgramData\Anaconda3\envs\geospatial\lib\site-packages\libmambapy\__init__.py", line 7, in <module>
raise e
File "C:\ProgramData\Anaconda3\envs\geospatial\lib\site-packages\libmambapy\__init__.py", line 4, in <module>
from libmambapy.bindings import * # noqa: F401,F403
ImportError: DLL load failed while importing bindings: La procΓ©dure spΓ©cifiΓ©e est introuvable.
(geospatial) PS C:\Users\DELL>
Additional info:
- OS: Windows10 (win64)
- Conda version: 4.13.0
- Conda-build: 3.21.4
- Python (env): 3.9.12
- Mamba 0.24.0
- Geopandas: 0.9.0
I already faced this very issue the day before, following the same procedure. In this session, I tried to start again from scratch, cleaned up the mess (deleted previous env), started new env and followed same steps and got the same error.
PS: Looked into closed #249 but nothing usefull.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Reactions: 10
- Comments: 24 (2 by maintainers)
Commits related to this issue
- fix: Update master_env to fix mamba crash The workaround is to specify libarchive. See https://github.com/mamba-org/mamba/issues/1728 — committed to RIVM-bioinformatics/juno-typing by KHajji 2 years ago
- Update mincoda base image to fix mamab error: https://github.com/mamba-org/mamba/issues/1728 — committed to gerlichlab/hicognition by cchlanger a year ago
- Update Dockerfile https://github.com/mamba-org/mamba/issues/1728 — committed to dwr-psandhu/conda-pack-docker by dwr-psandhu a year ago
I faced the same issue when I tried to build a conda package using βboaβ The command was:
conda mambabuild ./conda.recipe/ --output-folder /tmp/__localbuild__/conda/ --no-test -qThe error:I compare a healthy environment with the unhealthy environment and there are 3 diffs: healthy vs unhealthy libarchive 3.5.2 hb890918_2 vs libarchive 3.5.2 h5de8990_0 lzo 2.10 vs None tk 8.6.11 h1ccaba5_1 vs tk 8.6.12 h1ccaba5_0
I suspect that somehow the libarchive was corrupted by someone⦠As a workaround, the following command solved the issue:
mamba install libarchive=3.5.2=hb890918_2 -yInstalling mamba 1.4.6, 1.4.7 or 1.4.9 directly triggered the same
libarchive.so.13error for me. However, somehow for me it seems to be working after installing mamba 1.4.5, and then updating to 1.4.9.Note that Conda should not be installed to environments other than base though. See https://mamba.readthedocs.io/en/latest/user_guide/troubleshooting.html#mamba-should-be-installed-to-the-base-environment
Hi everyone, please stop adding new comments that donβt provide any new insights other than youβre also affected. Comments will notify everyone in this thread. Please use emoji reactions instead.
I am currently seeing this issue with both the conda-forge and defaults channel. Running
mamba install libarchive=3.5.2=hb890918_2 -yalso results in the same error for me. Anyone got any suggestions?I also experienced the same
ImportError: libarchive.so.13: cannot open shared object file: No such file or directoryproblem.libarchivefromdefaultschannel seems broken but the one fromconda-forgeis working.So this install line resulted in a broken mamba for me:
conda install mamba -n base -c defaults -c conda-forge.But this install line worked (switched channels priority order):
conda install mamba -n base -c conda-forge -c defaults.The side-effect is the entire
baseenv is now updated to conda-forge version. Hope there is no negative effect.Fix (working) but half measure
I tried removing mamba package and reinstalling it:
The half mesure:
An anterior version of mamba is installed (
mamba 0.15.3) instead of the latest update (mamba 0.24.0) as when mamba was first installed before installinggeopandas.Re-installation log
Click to expand re-installation log