PilotEdge Forums

Hello and Happy New Year!

Do you know of any issues using XPlane 9 with the PE client with Ubuntu 15.10 64bits?

I'm building a quick Sim for my Instrument rating...

Thanks.

X-Plane 9 is a 32-bit application.

Yep, I have installed Ubuntu 32bits.

Keith, does the PE client work ok with Ubuntu 15.10 32bits and XPlane 9?

Thanks,

The plugin isn't built for a particular linux distro. As long as you can run 32-bit plugins, my guess is you'll be ok. Every now and then we run into some strange compatibility issues with various versions of libc, but by and large it seems to be working ok.

I have installed but this is what I get (XP9 log.txt):

dlerror:/home/alexplane/X-Plane 9/Resources/plugins/PilotEdge/lin.xpl: undefined symbol: __stack_chk_fail_local
OpenAL version : 1.1
OpenAL hardware : OpenAL Soft
OpenAL extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_DEDICATED ALC_EXT_disconnect ALC_EXT_EFX ALC_EXT_thread_local_context ALC_SOFTX_device_clock ALC_SOFTX_HRTF ALC_SOFT_loopback ALC_SOFTX_midi_interface ALC_SOFT_pause_device


Any idea on how to fix it?

Thanks!

Suspect this could be your welcome to Linux evolution and resolution through symbolic linking. My real world experience running Linux X-Plane was on version 10.2x. Back when I tried this found a number of links that had to be created for my Unbuntu distro. Note, XP10 was re-linked with newer library versions when Steam support was added thus making this easier. For your case you have an older application (XP9) trying to work with much later library versions.

I also ran into to "issues" when the PPT was not assigned to a physical button. Which for me wasn't a problem since I have a Yoke. I was never able to get it to work with a PTT key.

After reviewing some of my notes I remembered that I was NEVER able to get PE to work on the 32 bit version. Successful PE tests didn't happen until I switched to the 64 bit version.
viewtopic.php?f=12&t=4414&start=10#p28866

Confirm the length of the call sign used to log onto PE. If long, try a shorter ID of 5 characters or less.

Which video drivers are you using (Nvidia, Radon, Mesa)?

Confirm that you have installed Open-AL (sound) on this Linux. Good idea to confirm that sound actually works.

Under "Gathering the required libraries";
http://www.x-plane.com/?article=linux-i ... alkthrough

Check for missing libraries and undefined symbols with the "ldd" command. See troubleshooting under the X-plane linux walk through. If there are undefined symbols these will need symbolic links. Once this is done for X-plane executable itself it will need to be repeated for the PE plugin (lin.xpl). It will be necessary to pick the correct version for the OS (32 bit or 64 bit) in use. The 32 bit version should be in the PE root level. The 64 bit version will be in the /64 directory.

For the PE plugin the command should look something like:

ldd "./home/alexplane/X-Plane 9/X-Plane.exe"
ldd "./home/alexplane/X-Plane 9/Resources/plugins/PilotEdge/lin.xpl"

As a reminder that under Linux it's quite possible to mix/match 32 bit and 64 bit libraries on the same PC. Linux doesn't always give much trouble shooting help should this be done incorrectly. IMO this is more likely to happen when trying to run a 32 bit application on a 64 bit OS. Running a 32 bit application on a 32 bit OS does improve the odds of success.

If there are no undefined symbols from the "ldd" command, then further trouble shooting is likely over my Linux head. Sorry.

>>
Troubleshooting
If, when trying to run the installer from the command line, an error about a missing library (for instance, libopenal) appears, try searching the operating system’s package manager for the missing file. If that fails, search Google with the library name and the name of the Linux distribution.

To quickly determine what libraries will be needed to run the installer, use the

ldd ./[installer name]

command in a terminal (after moving to that directory with the “cd” command).
<<

TexFly wrote:I'm building a quick Sim for my Instrument rating...

IMO using "quick" and "Linux" is the same sentence is a Myth. Adding "un-supported application" into this mix could make it even more difficult.

wmburns thank you so much for taking the time to help!

I ran the ldd command and this is what I got

alexplane@AleXPlane:~/X-Plane 9/Resources/plugins/PilotEdge$ ldd ./lin.xpl
linux-gate.so.1 => (0xb774e000)
libGL.so.1 => /usr/lib/libGL.so.1 (0xb75ab000)
libGLU.so.1 => /usr/lib/i386-linux-gnu/libGLU.so.1 (0xb7538000)
libpng12.so.0 => /lib/i386-linux-gnu/libpng12.so.0 (0xb750b000)
libts3client_linux_x86.so => not found
libnvidia-tls.so.340.96 => /usr/lib/tls/libnvidia-tls.so.340.96 (0xb7506000)
libnvidia-glcore.so.340.96 => /usr/lib/libnvidia-glcore.so.340.96 (0xb4f72000)
libX11.so.6 => /usr/lib/i386-linux-gnu/libX11.so.6 (0xb4e27000)
libXext.so.6 => /usr/lib/i386-linux-gnu/libXext.so.6 (0xb4e11000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb4c56000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xb4c51000)
libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb4ada000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb4a8d000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb4a6e000)
libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xb4a53000)
libxcb.so.1 => /usr/lib/i386-linux-gnu/libxcb.so.1 (0xb4a2e000)
/lib/ld-linux.so.2 (0x800a4000)
libXau.so.6 => /usr/lib/i386-linux-gnu/libXau.so.6 (0xb4a2a000)
libXdmcp.so.6 => /usr/lib/i386-linux-gnu/libXdmcp.so.6 (0xb4a23000)


Also the OpenAl library appears to be installed as you can see from the log.txt in my first post...

From the ldd output the following module is NOT being found.

libts3client_linux_x86.so => not found

However if you look at the directory structure the file is clearly visible in the /32 directory. It appears the PE plugin is not searching the /32 directory to find the team speak modules.

Note, during my Linux/XP10/PE testing I encountered the same error message using the 32 bit version. I was using XP10 and a different Unbuntu version. As i know the 64 bit PE plugin works, this seems to point at an "issue" with the 32 bit PE plugin version (or team speak?). Some of the Google searches tend to indicate the __stack_chk_fail_local could be cause by use of the linker "ld" instead of "gcc".

https://erl1.wordpress.com/2009/11/16/r ... untu-9-10/

Keith, is this something you can help with?

What may be an option for testing is to copy the contents of the /32 directory up a level to the PE root. Re-run the ldd command to see if this resolves the missing symbol. Be sure to match the file permissions.

I'm assuming that you also checked the X-plane executable for un-resolved symbols as well.

I did check the X-Plane exe and found no errors.

I copied the libts3client_linux_x86.so up a level with no luck. I think we need to have Keith telling us where lin.xpl is looking so to drop the file in that directory to test. Ideally we would have a "corrected" lin.xpl...Hopefully he will read this soon.


Just for the record...the PE plugin doesn't even load (not showing on the XP plugins menu).

Thanks!

the libts3client being 'missing' is a red herring. It's only that way because you're running the LDD command from the same folder as the plugin. In fact, X-Plane will be loading it with the current working directory set to the xplane root directory. If you run the LDD command from the xplane root directory, it'll find the TS3 library. It is not the source of your issue. If there was a library missing at run time, you'd have a different error message.

I recall this being an issue that was previously discussed on in the forum. It has to do with the specific version of libc if memory serves. Try searching for the key elements of the error message within the forum, I know we had a long discussion about it a little while ago.