roslaunch failing to launch webots_ros simulations
Hi everyone, I'm learning to use ros in integration with webots and I'm taking my first steps. I'm running ROS melodic on Ubuntu 18.04, I followed all the steps described in the first tutorials to configure my ros environment, but everytime I try to roslaunch one of the webots simulation contained in "webots_ros" package webots just opens and crashs subsequently and I get this error in the terminal.
roslaunch webots_ros complete_test.launch
... logging to /home/pinzers/.ros/log/0494a2fa-81e2-11eb-b805-6036dded622d/roslaunch-ubuntu-di-pinzers-4476.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://ubuntu-di-pinzers:33355/
SUMMARY
========
PARAMETERS
* /rosdistro: melodic
* /rosversion: 1.14.10
NODES
/
complete_test (webots_ros/complete_test)
webots (webots_ros/webots_launcher.py)
auto-starting new master
process[master]: started with pid [4486]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to 0494a2fa-81e2-11eb-b805-6036dded622d
process[rosout-1]: started with pid [4497]
started core service [/rosout]
process[webots-2]: started with pid [4504]
process[complete_test-3]: started with pid [4505]
Could not open file: '/opt/ros/melodic/share/webots_ros/worlds/complete_test.wbt'.
================================================================================REQUIRED process [webots-2] has died!
process has finished cleanly
log file: /home/pinzers/.ros/log/0494a2fa-81e2-11eb-b805-6036dded622d/webots-2*.log
Initiating shutdown!
================================================================================
[complete_test-3] killing on exit
[webots-2] killing on exit
[ INFO] [1615409336.882603859]: User stopped the 'complete_test' node.
[rosout-1] killing on exit
[master] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done
Can you confirm that the
/opt/ros/melodic/share/webots_ros/worlds/complete_test.wbt
file exists? Also, can you run it withwebots /opt/ros/melodic/share/webots_ros/worlds/complete_test.wbt
?Hello, I have the same problem as the above comment, and I do have the file you are asking about, and using webots does run the file. But I get error through using roslaunch:
WEBOTS_HOME environment variable not defined.
REQUIRED process [webots-2] has died! process has died [pid 35908, exit code 1, cmd /home/$user/webots_ws/devel/lib/webots_ros/webots_launcher.py --world=/home/$user/webots_ws/src/webots_ros/worlds/keyboard_teleop.wbt --mode=realtime --no-gui=false, --stream=false __name:=webots __log:=/home/$user/.ros/log/99ad7002-86b8-11ec-9497-0d0b6e064a0a/webots-2.log]. log file: /home/$user/.ros/log/99ad7002-86b8-11ec-9497-0d0b6e064a0a/webots-2*.log
Initiating shutdown!
After declaring WEBOTS_HOME variable to the location of my webots, it says that permission was denied, followed by the same webots has died message
Hello, I have the same problem as the above comment, and I don't have the file you are asking about. What should I do?
I have a similar problem...
WEBOTS_HOME environment variable not defined. ================================================================================REQUIRED process [webots-2] has died! process has died [pid 37402, exit code 1, cmd /opt/ros/noetic/lib/webots_ros/webots_launcher.py --world=/home/tractor2/webots_ws/src/Robotics_PicoDegree/bringup/worlds/4_wheels_robot_fully_loaded.wbt --mode=realtime --no-gui=false, --stream=false __name:=webots __log:=/home/tractor2/.ros/log/ca1d237a-6e81-11ed-b77d-e55309d439a2/webots-2.log]. log file: /home/tractor2/.ros/log/ca1d237a-6e81-11ed-b77d-e55309d439a2/webots-2*.log
Initiating shutdown!
I found this thread and tried $ webots /opt/ros/noetic/share/webots_ros/worlds/complete_test.wbt
This command did not work as it appears my graphics card did not meet requirements.
Any suggestions?
You should check the Webots System Requirements to fix this problem. Webots runs fine on any fairly recent hardware. The problem may come from a misconfiguration of your OpenGL drivers.