ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
I found one possible cause/solution to this problem in this blog post: Running ROS on Windows 10. The problem was that the LIBGL_ALWAYS_INDIRECT flag was set to 1. As per the blog post:
it is not possible to launch rviz when this indirection is active
Setting it to 0 fixed the problem for me and allowed me to run rviz properly:
export LIBGL_ALWAYS_INDIRECT=0
You can check what it is currently set to using:
echo $LIBGL_ALWAYS_INDIRECT
It seems that every new WSL (I assume you are using WSL to run Linux/ROS on Windows) shell defaults this flag to 1. So you may need to add this command to your .bashrc
file.
2 | No.2 Revision |
I found one possible cause/solution to this problem in this blog post: Running ROS on Windows 10. The problem was that the LIBGL_ALWAYS_INDIRECT flag was set to 1. As per the blog post:
it is not possible to launch rviz when this indirection is active
Setting it to 0 fixed the problem for me and allowed me to run rviz properly:
export LIBGL_ALWAYS_INDIRECT=0
You can check what it is currently set to using:
echo $LIBGL_ALWAYS_INDIRECT
It seems that every new WSL (I assume you are using WSL to run Linux/ROS on Windows) shell defaults this flag to 1. So you may need to add this the export command to your .bashrc
file.
3 | No.3 Revision |
I found one possible cause/solution to this problem in this blog post: Running ROS on Windows 10. The problem was that the LIBGL_ALWAYS_INDIRECT flag was set to 1. As per the blog post:
it is not possible to launch rviz when this indirection is active
Setting it to 0 fixed the problem for me and allowed me to run rviz properly:
export LIBGL_ALWAYS_INDIRECT=0
You can check what it is currently set to using:
echo $LIBGL_ALWAYS_INDIRECT
It seems that every new WSL (I assume you are using WSL to run Linux/ROS on Windows) shell defaults this flag to 1. So you may need to add the export command to your .bashrc
file.
I should also mention that setting this flag to 0 means I can run Rviz for the turtle sim tutorial, but not on it's own, and I do still see the error. The only difference is that with it set to 0, Rviz will actually launch with this command:
rosrun rviz rviz -d `rospack find turtle_tf`/rviz/turtle_rviz.rviz
4 | No.4 Revision |
I found one possible cause/solution to this problem in this blog post: Running ROS on Windows 10. The problem was that the LIBGL_ALWAYS_INDIRECT flag was set to 1. As per the blog post:
it is not possible to launch rviz when this indirection is active
Setting it to 0 fixed the problem for me and allowed me to run rviz properly:
export LIBGL_ALWAYS_INDIRECT=0
You can check what it is currently set to using:
echo $LIBGL_ALWAYS_INDIRECT
It seems that every new WSL (I assume you are using WSL to run Linux/ROS on Windows) shell defaults this flag to 1. So you may need to add the export command to your .bashrc
file.
I should also mention that setting this flag to 0 means I can run Rviz for the turtle sim tutorial, but not on it's own, and I do still see the error. The only difference is that with it set to 0, Rviz will actually launch with this command: launch.
rosrun rviz rviz -d `rospack find turtle_tf`/rviz/turtle_rviz.rviz