libGL error: MESA-LOADER: failed to open iris #81
Comments
|
Hi @HosameldinMohamed, this issue may be a better place where to discuss the problem you are experiencing. Could you provide as additional info:
Thanks! |
conda listconda infoenv |
This one seems quite messy. If you install Gazebo from source, probably you also need to remove the |
|
@traversaro Yes I went through the bashrc and removed the setup all the setup files related to the other Gazebo installation Here's the new envI am not able to launch the Gazebo from miniforge anymore. I don't know if it's seem related to this issue, but I put the result here: Gazebo launch errorMaybe I should make a fresh installation of Gazebo again. |
You could try that. In the meanwhile, can you provide the exact info on the distro used? I remember it was something Arch-based, but if you could report it it may help. |
Yes, |
traversaro
changed the title
|
@HosameldinMohamed I renamed the issue as now the blocking error is another. |
|
@wolfv reported a similar problem in Fedora 34, see: The workaround proposed by @nehaljwani was to run the application as: The rationale here is that the Intel iris driver is requiring a version of the libstdc++ that is more recent that the one provided in conda-forge. The workaround proposed is to (temporary) used the system libstdc++ instead of the one provided by conda-forge, at least until conda-forge is updated to use the new GCC/libstdc++ . Why this happens in Fedora 34 or in Manjaro Linux 21.0.6 ? Probably because both are fairly recent distribution with a fairly recent Intel iris driver. In the case of Manjaro, assuming that the system |
|
Once conda-forge ships GCC 11.1 this issue should be resolved. |
|
From what I understand, GCC 11 was packaged in conda-forge/ctng-compilers-feedstock#53 and several recent PRs. I did not fully understand the relation between how this packages and the @HosameldinMohamed error are related, but if @HosameldinMohamed wants to try again with a clean environment and check if the problem is solved it may be a good thing to test. |
@traversaro I've tried again with a clean environment and |
|
awesome! |
|
Great, I guess we can close the issue the n! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue:
In a non-deterministic way, Gazebo sometimes fails to spawn with the error:
Originally reported by @HosameldinMohamed in ami-iit/training-conda-robotics#2 (comment) .
Environment (
conda list):@HosameldinMohamed can you provide the
conda infoon the environment in which you are experiencing this?Details about
condaand system (conda info):@HosameldinMohamed can you provide the
conda infoon the environment in which you are experiencing this?The text was updated successfully, but these errors were encountered: