From: Douglas S. B. <db...@br...> - 2006-06-29 04:31:21
|
Friends of Gazebo, I'm trying to run Gazebo-0.6.0-rc1 (from tar.gz) on FC5 with Player/Stage 2.0.2 (out of CVS). I have installed GDAL (but not Proj4 or Lib3ds). I'm running with Livna nVIDIA drivers, and everything compiles fine. All looks good until: $ wxgazebo /usr/local/share/gazebo/worlds/pioneer2at.world starting server waiting for server connecting to server opening simulator interface ** Gazebo 0.6.0-rc1 ** * Part of the Player/Stage Project [http://playerstage.sourceforge.net]. * Copyright 2000-2005 Brian Gerkey, Richard Vaughan, Andrew Howard, * Nate Koenig and contributors. * Released under the GNU General Public License. using display [:0.0] rendering: [GLXP pbuffer] direct [yes] RGBA [8 8 8 0] depth [24] rendering: [GLXP pbuffer] direct [yes] RGBA [8 8 8 0] depth [24] server id [0] waiting for data And it never does anything besides this. I tried starting player, and then playerv, but no window appears. Strangely: $ gazebo /usr/local/share/gazebo/worlds/pioneer2at.world ** Gazebo 0.6.0-rc1 ** * Part of the Player/Stage Project [http://playerstage.sourceforge.net]. * Copyright 2000-2005 Brian Gerkey, Richard Vaughan, Andrew Howard, * Nate Koenig and contributors. * Released under the GNU General Public License. using display [:0.0] rendering: [GLXP pbuffer] direct [yes] RGBA [8 8 8 0] depth [24] rendering: [GLXP pbuffer] direct [yes] RGBA [8 8 8 0] depth [24] server id [0] Segmentation fault I think I just got a clue. /var/messages says: Jun 29 00:24:00 mightymouse kernel: audit(1151555040.854:39): avc: denied { execmod } for pid=11577 comm="gazebo" name="libode.so" dev=dm-0 ino=3305522 scontext=user_u:system_r:unconfined_t:s0 tcontext=system_u:object_r:lib_t:s0 tclass=file Jun 29 00:25:03 mightymouse kernel: audit(1151555103.642:40): avc: denied { execmod } for pid=11635 comm="wxgazebo" name="_gazebo.so" dev=dm-0 ino=4016682 scontext=user_u:system_r:unconfined_t:s0 tcontext=user_u:object_r:lib_t:s0 tclass=file Looks like gazebo and libode are triggering something in SELinux. Anyone know what special "chcon" commands I might need to run? I'll try turning SELinux off too to see if that helps... at least temporarily... -Doug -- Douglas S. Blank Computer Science Assistant Professor Bryn Mawr College (610)526-6501 http://cs.brynmawr.edu/~dblank |