I am using ROS Indigo with ros-indigo-gazebo5-ros-* installed. I was using the hector_quadrotor_gazebo package, and per the wiki instructions, I re-built everything from source to ensure compatibility. This worked very well for several months.

Recently, after an apt-get update and apt-get upgrade, my simulation no longer functions. I get this error:

core service [/rosout] found
process[spawn_robot-1]: started with pid [3537]
process[robot_state_publisher-2]: started with pid [3538]
/opt/ros/indigo/lib/robot_state_publisher/robot_state_publisher
process[ground_truth_to_tf-3]: started with pid [3579]
process[controller_spawner-4]: started with pid [3621]
[INFO] [WallTime: 1435259586.341210] [0.000000] Loading model xml from ros parameter
[INFO] [WallTime: 1435259586.350827] [0.000000] Waiting for service /gazebo/spawn_urdf_model
[INFO] [WallTime: 1435259586.354584] [1221.026000] Calling service /gazebo/spawn_urdf_model
[INFO] [WallTime: 1435259586.456276] [1221.128000] Controller Spawner: Waiting for service controller_manager/load_controller
[INFO] [WallTime: 1435259586.865404] [1221.169000] Spawn status: SpawnModel: Successfully spawned model
[spawn_robot-1] process has finished cleanly
log file: /home/tmoore/.ros/log/2805a436-1b6e-11e5-ae0c-cd10309fc746/spawn_robot-1*.log
[INFO] [WallTime: 1435259587.670885] [1221.170000] Controller Spawner: Waiting for service controller_manager/switch_controller
[INFO] [WallTime: 1435259587.674071] [1221.170000] Controller Spawner: Waiting for service controller_manager/unload_controller
[INFO] [WallTime: 1435259587.676925] [1221.170000] Loading controller: controller/twist
Traceback (most recent call last):
  File "/opt/ros/indigo/lib/controller_manager/spawner", line 212, in <module>
    if __name__ == '__main__': main()
  File "/opt/ros/indigo/lib/controller_manager/spawner", line 190, in main
    resp = load_controller(name)
  File "/opt/ros/indigo/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 435, in __call__
    return self.call(*args, **kwds)
  File "/opt/ros/indigo/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 505, in call
    raise ServiceException("unable to connect to service: %s"%e)
rospy.service.ServiceException: unable to connect to service: [Errno 104] Connection reset by peer
[INFO] [WallTime: 1435259587.756492] [1221.170000] Shutting down spawner. Stopping and unloading controllers...
[WARN] [WallTime: 1435259591.759524] [1221.170000] Controller Spawner couldn't reach controller_manager to take down controllers. Waited for 3 second(s).
[controller_spawner-4] process has died [pid 3621, exit code 1, cmd /opt/ros/indigo/lib/controller_manager/spawner controller/twist --shutdown-timeout 3 __name:=controller_spawner __log:=/home/tmoore/.ros/log/2805a436-1b6e-11e5-ae0c-cd10309fc746/controller_spawner-4.log].
log file: /home/tmoore/.ros/log/2805a436-1b6e-11e5-ae0c-cd10309fc746/controller_spawner-4*.log

After some digging, I noticed that the ROS Ubuntu package servers are hosting ros-indigo-gazebo-ros-pkgs with version 2.4.8, whereas the OSRF servers have version 2.4.7 of ros-indigo-gazebo5-ros-pkgs. Assuming this is our issue, we can try pulling down the source for release 2.4.8 and building it against gazebo5 ourselves, but will there be an update to the OSRF-hosted packages?