Open smidm opened 7 months ago
can't reproduce this on Ubuntu 22.04
It seems that newer distributions are affected.
@smidm this is interesting though not particularly shocking to me.
Rerun is not a pure-python package and links against several system libraries. In a pip-based installation, the assumption is the wheel will pick those libraries up from the system. In a conda-based environment, the assumption is the conda-build tooling instead provides these dependencies.
When you mix pip and conda like this I assume the conda environment is causing Rerun to look to conda for the system deps, but they aren't provided by the conda environment.
Is there a reason that you can't just use the conda-provided package?
I can use the conda package perfectly well, but I wasn't aware of it's existence at first. Installing pip packages into conda is well supported use case and I haven't encountered similar problem before. I'm using pip installed packages in conda quite often.
Describe the bug
The rerun viewer fails to start when installed using pip in conda environment. The standalone executable, pip install in a pure python environment (not based on a conda installed python) or the conda package (
conda install -c conda-forge rerun-sdk
) in conda environment all work.what doesn't solve the problem:
rerun reset
WINIT_UNIX_BACKEND=x11
To Reproduce Steps to reproduce the behavior:
conda create --name rerun python=3.11 -y
conda activate rerun
pip install rerun-sdk
rerun
Expected behavior
viewer gui starts
Backtrace
Desktop (please complete the following information):
Rerun version
rerun_py 0.12.1 [rustc 1.74.0 (79e9716c9 2023-11-13), LLVM 17.0.4] x86_64-unknown-linux-gnu release-0.12.1 bef0d78, built 2024-01-17T16:50:34Z