gzserver segfaults

edit

New and up to date install of Kinetic and Ubuntu 16. I log in, open terminal and issue one command

roslaunch turtlebot_gazebo turtlebot_world.launch

and then gzserver segfaults.

I'm new to ROS but been into UNIX software development profesionally going back to the 1980's. It was always my opinion that if something I wrote segfaults it is always a bug, no matter what devious trick the user did to crash my software. I and my bosses figure I should have caught the problem with some kind of data validation or assert staetment.

Does the ROS development community have the same view on this? Should I report segfaults as bugs?

Next question are Where/how to report and most importantly, this is the very first step in the on-line totorial and it fails. How to figure out why?

Here is a cut and paste from the terminal window at the point where things start going wrong. (To address the question "what is in those .log files? The log files listed below do not exist. Apparently gazebo crashed before it could write to the log file.)

process[laserscan_nodelet_manager-9]: started with pid [18771]
process[depthimage_to_laserscan-10]: started with pid [18775]
[ INFO] [1481175480.361448318]: Finished loading Gazebo ROS API Plugin.
[ INFO] [1481175480.362918368]: waitForService: Service [/gazebo/set_physics_properties] has not been advertised, waiting...
Segmentation fault (core dumped)
[gazebo-2] process has died [pid 18708, exit code 139, cmd /opt/ros/kinetic/lib/gazebo_ros/gzserver -e ode /opt/ros/kinetic/share/turtlebot_gazebo/worlds/playground.world __name:=gazebo __log:=/home/chris/.ros/log/7977bfb0-bd08-11e6-a492-002100e558ce/gazebo-2.log].
log file: /home/chris/.ros/log/7977bfb0-bd08-11e6-a492-002100e558ce/gazebo-2*.log
[gazebo_gui-3] process has died [pid 18729, exit code 255, cmd /opt/ros/kinetic/lib/gazebo_ros/gzclient __name:=gazebo_gui __log:=/home/chris/.ros/log/7977bfb0-bd08-11e6-a492-002100e558ce/gazebo_gui-3.log].
log file: /home/chris/.ros/log/7977bfb0-bd08-11e6-a492-002100e558ce/gazebo_gui-3*.log