Installed ros-kinetic-turtlebot-gazebo but something weird
I think I am getting wrapped around the axle with respect to paths or apt-get so I thought I would ask this...
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install ros-kinetic-turtlebot-gazebo
source ~/catkin_ws/devel/setup.bash
and still when I do
roslaunch turtlebot_gazebo turtlebot_world.launch
I get an error because turtlebot_gazebo doesn't exist. roscd turtlebot_gazebo similarly doesn't work. Because I have turtlebot3 packages installed, I am able to see turtlebot3_gazebo but I believe that has nothing to do with anything. Can someone see where I am going wrong?
Updates (thanks @gvdhoorn)
I did the following to try and troubleshoot:
sudo apt-get remove turtlebot_gazebo
sudo apt-get update
sudo apt-get upgrade
sudo apt-get install turtlebot_gazebo
And thnings got better, but still weird. After that:
dpkg -l | grep turtlebot
ii ros-kinetic-turtlebot-bringup 2.4.2-0xenial-20180803-215945-0800 amd64 turtlebot_bringup provides roslaunch scripts for starting the TurtleBot base functionality.
ii ros-kinetic-turtlebot-capabilities 2.4.2-0xenial-20180516-155341-0800 amd64 Capabilities for the TurtleBot
ii ros-kinetic-turtlebot-description 2.4.2-0xenial-20180803-190853-0800 amd64 turtlebot_description provides a complete 3D model of the TurtleBot for simulation and visualization.
ii ros-kinetic-turtlebot-gazebo 2.2.3-0xenial-20180804-004347-0800 amd64 Gazebo launchers and worlds for TurtleBot simulation
ii ros-kinetic-turtlebot-navigation 2.3.7-0xenial-20180804-001200-0800 amd64 turtlebot_navigation
~/catkin_ws/src/rosbook$ rospack profile
Full tree crawl took 0.038709 seconds.
Directories marked with (*) contain no manifest. You may
want to delete these directories.
To get just of list of directories without manifests,
re-run the profile with --zombie-only
-------------------------------------------------------------
0.033712 /opt/ros/kinetic/share
0.003433 /home/pitosalas/catkin_ws/src
0.001256 /home/pitosalas/catkin_ws/src/turtlebot3
0.000575 /home/pitosalas/catkin_ws/src/turtlebot3_simulations
0.000362 * /opt/ros/kinetic/share/OpenCV-3.3.1-dev
0.000070 * /opt/ros/kinetic/share/OpenCV-3.3.1-dev/haarcascades
0.000069 * /opt/ros/kinetic/share/man
0.000052 * /opt/ros/kinetic/share/doc
0.000039 * /opt/ros/kinetic/share/OpenCV-3.3.1-dev/lbpcascades
0.000017 * /opt/ros/kinetic/share/man/man1
0.000011 * /opt/ros/kinetic/share/doc/liborocos-kdl
pitosalas@RpsUbuntu:~/catkin_ws/src/rosbook$ rospack find turtlebot
Now, gazebo crashes:
roslaunch turtlebot_gazebo turtlebot_world.launch
... logging to /home/pitosalas/.ros/log/b0dd6d1a-a3a2-11e8-86c8-002500efe1ca/roslaunch-RpsUbuntu-4793.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://RpsUbuntu:46543/
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.13
* /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)
auto-starting new master
process[master]: started with pid [4809]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to b0dd6d1a-a3a2-11e8-86c8-002500efe1ca
process[rosout-1]: started with pid [4822]
started core service [/rosout ...
this is a bit jumbled up, I'm guessing this needs to be three separate lines?
As always when checking why pkgs can't be found / appear not to be installed:
apt-get
: did it indicate successful installation?dpkg -l | grep turtlebot
?rospack profile
, thenrospack find turtlebot_gazebo
: does that work?I'm also assuming that you're
source
ing your base ROS installation / workspace before trying to runroslaunch
.Yes, and see updates above.Whoops. Seem to have exceeded allowed lengrh.
Theories: 1) turtlebot_* packages are actually not compatible with Kinetic.2) I also have turtlebot3 packages installed and they are interfering.