
Ok, here is the instalation:
[gma@localhost Descargas]$ pwd
/home/gma/Descargas
[gma@localhost Descargas]$ ./oo
oolite-1.80.linux-x86.run oolite-1.80-test.linux-x86.run
[gma@localhost Descargas]$ ./oolite-1.80.linux-x86.run
Verifying archive integrity... All good.
Uncompressing Oolite 1.80 ..............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
Install Oolite system-wide or in your home directory? [s/H]
Removing Oolite from "/home/gma/GNUstep/Applications/Oolite"... Done.
Warning 48: Some folders could not be removed.
Installing Oolite in "/home/gma/GNUstep/Applications/Oolite"...
Copying oolite executable and resources... Done.
Extracting documentation... Done.
Extracting dependencies... Done.
Generating startup and wrapper scripts... Done.
Updating desktop menu... Done.
Cleaning up temporary folders... Done.
Finished!
A desktop menu entry "Oolite (oolite.org)" has been added under Games.
To start Oolite from a shell, run "/home/gma/GNUstep/Applications/Oolite/oolite".
To uninstall Oolite, run "/home/gma/GNUstep/Applications/Oolite/uninstall".
[gma@localhost Descargas]$

Now try to run:
[gma@localhost Descargas]$
[gma@localhost Descargas]$ /home/gma/GNUstep/Applications/Oolite/oolite
It seems that your operating system does not have a valid timezone name
configured and is using an abbreviation instead. By comparing timezone
file data it is has been possible to find the actual timezone used, but
doing that is a slow process.
You can avoid slowness of this time zone detecting approach
by setting the environment variable TZ='Chile/Continental'
Or You can override the timezone name by setting the 'Local Time Zone'
NSUserDefault via the 'defaults' command line utility, a Preferences
application, or some other utility.
eg "defaults write NSGlobalDomain 'Local Time Zone' 'Chile/Continental'"
AL lib: (WW) alc_initconfig: Failed to initialize backend "pulse"
AL lib: (EE) ALSANoMMapProc: available update failed: Tubería rota
SNIP SNIP
SNIP SNIP
SNIP SNIP
AL lib: (EE) ALSANoMMapProc: available update failed: Tubería rota
AL lib: (EE) ALSANoMMapProc: available update failed: Tubería rota
AL lib: (EE) ALSANoMMapProc: available update failed: Tubería rota
intel_do_flush_locked failed: Error de entrada/salida
AL lib: (EE) ALSANoMMapProc: available update failed: Tubería rota
AL lib: (EE) alc_cleanup: 1 device not closed
Erk. It looks like Oolite died with an error. When making an error
report, please copy + paste the log above into the report.
(Press Ctrl-C to continue)

And now the LOGs:
Opening log for Oolite version 1.80 (x86-32) under Linux 3.4.52-pclos1 at 2015-05-17 17:33:53 -0400.
4 processors detected.
Build options: OpenAL, new planets.
Note that the contents of the log file can be adjusted by editing logcontrol.plist.
17:33:54.384 [dataCache.notFound]: No data cache found, starting from scratch.
17:33:54.648 [display.mode.list.native]: X11 native resolution detected: 1366 x 768
Closing log at 2015-05-17 17:33:55 -0400.

Thanks and have a good day
