launching gazebo fails with ros-groovy-pr2-interactive-manipulation
Hi,
I've just installed ROS groovy on the last Ubuntu LTS and I'm trying to run manipulation samples with PR2 (sorry I'm not authorized to add a real link but here it is: wiki.ros.org/pr2tabletopmanipulation_apps).
I start roscore, then launch
roslaunch manipulationworlds pr2table_object.launch
Which generates an error:
[...]
Gazebo multi-robot simulator, version 1.5.0
Copyright (C) 2013 Open Source Robotics Foundation.
Released under the Apache 2 License.
process[wide_stereo/wide_stereo_proc-7]: started with pid [21116]
process[narrow_stereo/narrow_stereo_proc-8]: started with pid [21119]
process[narrow_stereo_textured/narrow_stereo_textured_proc-9]: started with pid [21163]
Msg Waiting for master.process[left_image_raw_relay-10]: started with pid [21209]
Warning [ModelDatabase.cc:290] Getting models from #######. This may take a few seconds.
.loading model xml from ros parameter
process[right_image_raw_relay-11]: started with pid [21246]
[INFO] [WallTime: 1389784681.281631] [0.000000] waiting for service /gazebo/spawn_urdf_model
.process[left_camera_info_relay-12]: started with pid [21304]
process[right_camera_info_relay-13]: started with pid [21320]
.process[r_forearm_cam/image_proc-14]: started with pid [21382]
process[l_forearm_cam/image_proc-15]: started with pid [21446]
.process[diag_agg-16]: started with pid [21497]
.process[pr2_dashboard_aggregator-17]: started with pid [21613]
.process[robot_pose_ekf-18]: started with pid [21729]
..process[base_hokuyo_node-19]: started with pid [21840]
.process[tilt_hokuyo_node-20]: started with pid [21964]
.process[tf2_buffer_server-21]: started with pid [22085]
..process[camera_synchronizer_node-22]: started with pid [22203]
.process[default_controllers_spawner-23]: started with pid [22322]
.[ INFO] [1389784694.008928303]: Starting to spin camera_synchronizer at 100.000000 Hz...
process[r_gripper_controller/gripper_action_node-24]: started with pid [22429]
..process[l_gripper_controller/gripper_action_node-25]: started with pid [22543]
.process[head_traj_controller/point_head_action-26]: started with pid [22651]
..process[torso_controller/position_joint_action_node-27]: started with pid [22734]
.process[spawn_table-28]: started with pid [22834]
..process[spawn_object-29]: started with pid [22931]
..process[sor_pgs_iters-30]: started with pid [23037]
.terminate called after throwing an instance of 'ros::InvalidNameException'
what(): Character [#] at element [8] is not valid in Graph Resource Name [gazeboeb#]. Valid characters are a-z, A-Z, 0-9, / and _.
process[sor_pgs_w-31]: started with pid [23135]
process[time_step-32]: started with pid [23211]
Error [Connection.cc:477] Connection[0] Closed during Read
Aborted (core dumped)
[gazebo-1] process has died [pid 21049, exit code 134, cmd /opt/ros/groovy/stacks/simulator_gazebo/gazebo/scripts/gazebo -u /opt/ros/groovy/stacks/simulator_gazebo/gazebo_worlds/worlds/empty.world __name:=gazebo __log:=/home/rosie/.ros/log/a363ff42-7dd6-11e3-902e-0800276d379e/gazebo-1.log].
log file: /home/rosie/.ros/log/a363ff42-7dd6-11e3-902e-0800276d379e/gazebo-1*.log
terminate called after throwing an instance of 'boost::system::system_error'
what(): Connection reset by peer
loading model xml from ros parameter
[INFO] [WallTime: 1389784713.186396] [0.000000] waiting for service /gazebo/spawn_urdf_model
Aborted (core dumped)
[gazebo_gui-2] process has died [pid 21054, exit code 134, cmd /opt/ros/groovy/stacks/simulator_gazebo/gazebo/scripts/gui __name:=gazebo_gui __log:=/home/rosie/.ros/log/a363ff42-7dd6-11e3-902e-0800276d379e/gazebo_gui-2.log].
log file: /home/rosie/.ros/log/a363ff42-7dd6-11e3-902e-0800276d379e/gazebo_gui-2*.log
Note: concerning the ros::InvalidNameException I replaced the invalid character by a #, but the original character is represented as the 0018 code.
Could you help me with that? The logs gazebo_gui-1 and 2 do not exist. I assume the crash is link with the exception above but I can't find any ...
Did you ever find a solution to this? I've reproduced this issue on 4 machines, while other machines just work, with no explanation at all. Mine also uses the 0018 character code, but it's gazebobo# instead of gazeboeb. It obviously doesn't exist anywhere; my thought is that it's somehow reading the launch files in a corrupted way? But this is only a problem for the gazebo launch files.