Trace:

Differences

This shows you the differences between two versions of the page.

--- projects:hands_on_examples_gazebo_intel [2012/07/19 15:09] – created winklerj
+++ projects:hands_on_examples_gazebo_intel [2012/07/19 15:11] (current) – Added BG info on gazebo client ui winklerj
@@ Line 1: / Line 1: @@
+====== Workarounds for Gazebo Intel Graphics Card Issues ======
+===== Segmentation faults =====
+If you encounter the error
+<code>[gazebo_gui-19] process has died [pid 6086, exit code 139, cmd /opt/ros/fuerte/stacks/simulator_gazebo/gazebo/scripts/gui __name:=gazebo_gui __log:=/home/winkler/.ros/log/ba357cea-d1b2-11e1-b926-8c705ac51404/gazebo_gui-19.log].
+log file: /home/winkler/.ros/log/ba357cea-d1b2-11e1-b926-8c705ac51404/gazebo_gui-19*.log</code> or similar and you're running on a system with only an Intel graphics card, setting the following ENV variable might reduce the frequency in which this error comes up:
+<code>export OGRE_RTT_MODE=Copy</code>
+Just add it to your ~/.bashrc.
+===== Rough background info =====
+The command that actually fails with a segfault is the following:
+<code>`rospack find gazebo`/gazebo/bin/gzclient -g `rospack find gazebo`/lib/libgazebo_ros_paths_plugin.so</code>
+Once Gazebo launched (but did not display the GUI window) you can run this command to open the gazebo client ui window (instead of launching the gazebo master again).