Unable to run Gazebo with ROS kinetic

asked 2019-05-29 20:17:23 -0500

logan.ydid gravatar image

Hello,

I have been following the tutorials in the Programming Robots with ROS book and I have hit a snag. I have gotten to the part where we first attempt to simulate a turtlebot in Gazebo. When I try to run the terminal command from the book;roslaunch turtlebot_gazebo turtlebot_world.launch I end up with [gazebo -1] process has died [pid 9621... After much online searching, to no avail, I decided to completely do a fresh install of ubuntu and ROS. However, I seem to still be getting the same error.

For my specs I am running ubuntu 16.04 LTS on an HP-mini-110 with a 1.6GHz dual core intel atom CPU and an intel 945GME graphics processor. I know that its not super powerful but I hope thats not the issue.

See below for the full output from the terminal leading up to the error. It mentions something about a log file but it doesn't seem to exist, at least not where it says.

    art@art-HP-Mini-110-1100:~/.ros/log/60fd69d0-7f0c-11e9-813a-0ceee68c4bed$ roslaunch turtlebot_gazebo turtlebot_world.launch
... logging to /home/art/.ros/log/60fd69d0-7f0c-11e9-813a-0ceee68c4bed/roslaunch-art-HP-Mini-110-1100-15373.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt

Done checking log file disk usage. Usage is <1GB.

xacro: Traditional processing is deprecated. Switch to --inorder processing!
To check for compatibility of your document, use option --check-order.
For more infos, see http://wiki.ros.org/xacro#Processing_Order
xacro.py is deprecated; please use xacro instead
started roslaunch server http://art-HP-Mini-110-1100:38215/

SUMMARY
========

PARAMETERS
 * /bumper2pointcloud/pointcloud_radius: 0.24
 * /cmd_vel_mux/yaml_cfg_file: /opt/ros/kinetic/...
 * /depthimage_to_laserscan/output_frame_id: /camera_depth_frame
 * /depthimage_to_laserscan/range_min: 0.45
 * /depthimage_to_laserscan/scan_height: 10
 * /robot_description: <?xml version="1....
 * /robot_state_publisher/publish_frequency: 30.0
 * /rosdistro: kinetic
 * /rosversion: 1.12.14
 * /use_sim_time: True

NODES
  /
    bumper2pointcloud (nodelet/nodelet)
    cmd_vel_mux (nodelet/nodelet)
    depthimage_to_laserscan (nodelet/nodelet)
    gazebo (gazebo_ros/gzserver)
    gazebo_gui (gazebo_ros/gzclient)
    laserscan_nodelet_manager (nodelet/nodelet)
    mobile_base_nodelet_manager (nodelet/nodelet)
    robot_state_publisher (robot_state_publisher/robot_state_publisher)
    spawn_turtlebot_model (gazebo_ros/spawn_model)

ROS_MASTER_URI=http://localhost:11311

process[gazebo-1]: started with pid [15400]
process[gazebo_gui-2]: started with pid [15402]
process[spawn_turtlebot_model-3]: started with pid [15410]
process[mobile_base_nodelet_manager-4]: started with pid [15411]
process[cmd_vel_mux-5]: started with pid [15412]
process[bumper2pointcloud-6]: started with pid [15413]
process[robot_state_publisher-7]: started with pid [15414]
process[laserscan_nodelet_manager-8]: started with pid [15415]
process[depthimage_to_laserscan-9]: started with pid [15416]
[ INFO] [1559175098.446825532]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1559175098.455395173]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
[ INFO] [1559175099.021084819]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1559175099.026340125]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
Segmentation fault (core dumped)
[gazebo-1] process has died [pid 15400, exit code 139, cmd /opt/ros/kinetic/lib/gazebo_ros/gzserver -e ode /opt/ros/kinetic/share/turtlebot_gazebo/worlds/playground.world __name:=gazebo __log:=/home/art/.ros/log/60fd69d0-7f0c-11e9-813a-0ceee68c4bed/gazebo-1.log].
log file: /home/art/.ros/log/60fd69d0-7f0c-11e9-813a-0ceee68c4bed/gazebo-1*.log
Segmentation fault (core dumped)
[gazebo_gui-2] process has died [pid 15402, exit code 139, cmd /opt/ros/kinetic/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/home/art/.ros/log/60fd69d0-7f0c-11e9-813a-0ceee68c4bed/gazebo_gui-2.log].
log file: /home/art/.ros ...
(more)
edit retag flag offensive close merge delete

Comments

Can you please update your question with a page number?

jayess gravatar imagejayess ( 2019-05-29 21:51:13 -0500 )edit

sure thing! it was on page 125 of Programming Robots with ROS

logan.ydid gravatar imagelogan.ydid ( 2019-05-29 22:30:06 -0500 )edit

For my specs I am running ubuntu 16.04 LTS on an HP-mini-110 with a 1.6GHz dual core intel atom CPU and an intel 945GME graphics processor. I know that its not super powerful but I hope thats not the issue.

this may well be the problem, actually.

An i945 is barely a video card and the support for accelerated OpenGL is really minor. Gazebo is a heavy graphical application, relying on proper 3D acceleration to render just about everything (and sometimes even for GPU accelerating the simulation).

One thing to try could be to see whether Gazebo can start on its own (so without ROS involved). If it does, that still doesn't mean that everything should be fine: a full simulation running inside Gazebo will tax your system and could exercise parts of the simulator that an empty, stand-alone run doesn't.

If Gazebo stand-alone also doesn ...(more)

gvdhoorn gravatar imagegvdhoorn ( 2019-05-30 01:55:53 -0500 )edit

I'm assuming that you're using the gazebo_ros launch file. You can pass the verbose=true to the launch file and will start gazebo with more console outputs. That might give you a clue as to why it's seg faulting.

ChuiV gravatar imageChuiV ( 2019-06-06 09:08:57 -0500 )edit