Undefined symbol after upgrade to Gazebo 2.2.2 [closed]
I have essentially the same problem as listed in the following questions:
However the processes in Question 1 to fix do not resolve this issue, and it seems that an upgrade to the packages fixed the problem in Question 2. I upgraded to Hydro 2.2.2 yesterday and subsequently, previously working ROSLaunches fail with
Waiting for mastergzserver: symbol lookup error: /opt/ros/hydro
/lib/libgazebo_ros_api_plugin.so: undefined symbol: _ZN3ros7console5printEPNS0_10FilterBaseEPN7log4cxx6LoggerENS0_6levels5LevelEPKciS9_S9_z
[gazebo-2] process has died [pid 21975, exit code 127, cmd /opt/ros/hydro/lib/gazebo_ros/gzserver /home/petermilani/catkin_ws/src/qbot_gazebo/worlds/qbot.world __name:=gazebo __log:=/home/petermilani/.ros/log/8ef39554-bd32-11e3-8dc0-c43dc7c33e28/gazebo-2.log].
log file: /home/petermilani/.ros/log/8ef39554-bd32-11e3-8dc0-c43dc7c33e28/gazebo-2*.log
..............................
Error [ConnectionManager.cc:116] Failed to connect to master in 30 seconds.
Error [gazebo.cc:59] Unable to initialize transport.
Error [gazebo.cc:203] Unable to setup Gazebo
[gazebo_gui-3] process has died [pid 21980, exit code 255, cmd /opt/ros/hydro/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/home/petermilani/.ros/log/8ef39554-bd32-11e3-8dc0-c43dc7c33e28/gazebo_gui-3.log].
log file: /home/petermilani/.ros/log/8ef39554-bd32-11e3-8dc0-c43dc7c33e28/gazebo_gui-3*.log
Are there any other fixes or workarounds. I like the problem in Question 2, running ROS Hydro, on Ubuntu 12.04 with Gazebo 2.2.2. My GAZEBO_MODEL_PATH
is defined, the plugin path is not, however my ROS_PACKAGE_PATHS
are referencing hydro.
Any suggestions?
Peter