The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Our team ran into the similar/same rosrun issue on Ubuntu 16.04 with ROS Kinetic. TLDR, we fixed by installing ros-kinetic-rosbash and removed "upstream" version of rosbash. Command-wise it was:
apt-get purge rosbash && apt-get autoremove
apt-get install ros-kinetic-rosbash
We found in our case rosrun was provided by rosbash (NOT the one hosted on ros.org)
$ which rosrun
/usr/bin/rosrun
After having installed the one from ros.org, I see the path I expect:
$ which rosrun
/opt/ros/kinetic/bin/rosrun
(The reason we had the upstream rosbash installed was that we installed it manually by our mistake.)
| | 2 | No.2 Revision |
TLDR; Use ros-%ROS_DISTRO%-rosbash (e.g. ros-kinetic-rosbash) instead of rosbash.
Our team ran into the similar/same rosrun issue on Ubuntu 16.04 with ROS Kinetic. TLDR, we fixed by installing ros-kinetic-rosbash and removed "upstream" version of rosbash. Command-wise it was:
apt-get purge rosbash && apt-get autoremove
apt-get install ros-kinetic-rosbash
We found in our case rosrun was provided by rosbash (NOT the one hosted on ros.org)
$ which rosrun
/usr/bin/rosrun
After having installed the one from ros.org, I see the path I expect:
$ which rosrun
/opt/ros/kinetic/bin/rosrun
(The reason we had the upstream rosbash installed was that we installed it manually by our mistake.)
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.