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
For me, this manifested when trying to run the mars rover demo inside the space_robots image, although I suspect that the issue would manifest with anything that runs Gazebo.
Removing those lines makes the resulting space_robots image (which is built on top of space_ros) work correctly.
The text was updated successfully, but these errors were encountered:
@mkhansenbot has more information on this; he was the one who figured this out and told me what the solution was.
ivanperez-keera
changed the title
docker/space_robots does not run due to issues with graphics driver in spaceros
Gazebo won't start in space_robots due to issues with graphics driver in spacerosJan 9, 2024
@mkhansenbot The fix to this seems relatively simple, but I don't want to rush things to get them in the release unnecessarily. Do you think this should be in the next release?
If so, maybe I can send the PR that takes those lines out and you can review & approve.
Added to next milestone (proposed) humble-2024.04.0.
I think the immediate issue with the upstream driver has been fixed, at least on my system. However, we're open to future breaks in our simulation due to the fact we're always using the upstream driver. @EzraBrooks has suggested that we can pin to a mesa driver version. I think we should discuss that solution and fix in the next release.
The updated MESA driver in Space ROS makes it impossible to launch Gazebo.
The offending lines are:
docker/spaceros/Earthfile
Lines 91 to 93 in 76cd412
For me, this manifested when trying to run the mars rover demo inside the
space_robots
image, although I suspect that the issue would manifest with anything that runs Gazebo.Removing those lines makes the resulting
space_robots
image (which is built on top ofspace_ros
) work correctly.The text was updated successfully, but these errors were encountered: