ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

joehays's profile - activity

2021-04-08 02:48:53 -0500 received badge  Famous Question (source)
2020-12-22 19:27:59 -0500 received badge  Notable Question (source)
2020-12-22 19:27:59 -0500 received badge  Popular Question (source)
2020-10-29 07:29:59 -0500 received badge  Famous Question (source)
2020-09-22 08:48:12 -0500 received badge  Enthusiast
2020-09-03 19:25:17 -0500 received badge  Notable Question (source)
2020-09-01 12:01:48 -0500 commented question how to make ROS truly containerized in Docker?

Thanks for the comments. @gvdhoorn, not using the host network takes away my ability to X11 Forward (which I'm dependen

2020-09-01 10:48:15 -0500 commented answer No definition of [gazebo] for OS version [melodic]

<sheepish grin=""> changing '--os=ubuntu:melodic' to '--os=ubuntu:bionic' seemed to do it. Thanks for catching

2020-09-01 10:46:33 -0500 marked best answer No definition of [gazebo] for OS version [melodic]

I have a Ubuntu 18.04 docker image/container with ROS melodic and Gazebo 9 installed. When I try to run from the console within the docker container,

source devel/setup.bash && \
    rosdep fix-permissions && \
    rosdep update && \
    rosdep install --from-paths src --ignore-src -r --rosdistro=${ROS_DISTRO} -y --os=ubuntu:melodic

rosdep complains with,

[some package]: No definition of [gazebo] for OS version [melodic]

for a handful of packages.

I can successfully launch gazebo and load models but for some reason the 'rosdep install' step is failing to find gazebo.

Any ideas why?

2020-09-01 10:46:33 -0500 received badge  Scholar (source)
2020-09-01 10:46:28 -0500 received badge  Supporter (source)
2020-09-01 05:54:58 -0500 received badge  Popular Question (source)
2020-08-31 15:11:13 -0500 asked a question how to make ROS truly containerized in Docker?

how to make ROS truly containerized in Docker? I have a linux server that multiple developers access for development whe

2020-08-31 11:14:26 -0500 asked a question No definition of [gazebo] for OS version [melodic]

No definition of [gazebo] for OS version [melodic] I have a Ubuntu 18.04 docker image/container with ROS melodic and Gaz

2020-08-31 11:11:03 -0500 asked a question No definition of [gazebo] for OS version [melodic]

No definition of [gazebo] for OS version [melodic] I have a Ubuntu 18.04 docker image/container with ROS melodic and Gaz

2013-05-06 16:20:37 -0500 received badge  Favorite Question (source)
2013-05-06 16:20:36 -0500 received badge  Nice Question (source)
2013-05-02 03:38:17 -0500 received badge  Famous Question (source)
2013-05-01 16:22:53 -0500 received badge  Notable Question (source)
2013-05-01 14:39:41 -0500 received badge  Student (source)
2013-05-01 11:14:31 -0500 received badge  Popular Question (source)
2013-05-01 08:40:58 -0500 asked a question Why use ROS?

My organization is not currently using ROS but I am intrigued. I've proposed the idea of us using ROS and the pragmatists inevitably ask, "what's the value of switching to ROS?"

I have some thoughts/ideas on this but am not yet skilled in ROS. So, I thought I'd throw the question out to you the experts,

Why is ROS so great?

2012-10-23 09:06:59 -0500 received badge  Editor (source)
2012-10-23 09:01:39 -0500 answered a question Gazebo unable to launch empty world

I get a very similar result when running on a new install of ROS. I ran,

roslaunch gazebo_worlds empty_world.launch

and got,

Msg Connected to gazebo master @ http://localhost:11345
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  159 (GLX)
  Minor opcode of failed request:  5 (X_GLXMakeCurrent)
  Serial number of failed request:  19
  Current serial number in output stream:  19
Error [Transport.cc:102] Unable to get topic namespaces in [50] tries.
Error [Node.cc:68] No namespace found
/opt/ros/fuerte/stacks/simulator_gazebo/gazebo/scripts/gui: line 2:  2144 Segmentation fault      `rospack find gazebo`/gazebo/bin/gzclient -g `rospack find gazebo`/lib/libgazebo_ros_paths_plugin.so
[gazebo_gui-3] process has died [pid 2141, exit code 139, cmd /opt/ros/fuerte/stacks/simulator_gazebo/gazebo/scripts/gui __name:=gazebo_gui __log:=/home/jhays/.ros/log/6adeeafa-1d43-11e2-a747-842b2bbf9746/gazebo_gui-3.log].
log file: /home/jhays/.ros/log/6adeeafa-1d43-11e2-a747-842b2bbf9746/gazebo_gui-3*.log