PilotEdge Forums

It's odd that it's finding the TS3 plugin in /usr/lib for the 32-bit version. Can you try renaming the /usr/lib/libts3client_linux_x86.so to something else so it won't find it? It really needs to be using the library that we ship with.

Also, can you try running the ldd command from the X-Plane root directory? That is important as some of the libraries are linked with relative paths based on it being loaded from the xplane root (that's why the TS3 lib isn't found when you run the ldd on the 64-bit version. It'll find the library if you run it from the Xplane root).

FWIIW, I was never able to the the Unbuntu Linux 32 bit version with PE to work despite considerable effort. As I was able to get the 64 bit version to work (and my experience was very stable), it seemed pointless to continue work on the 32 bit version.

I tried the v1.1.1b 64-bit Linux plugin with Ubuntu 14.04 LTS and was unable to get it to work. The plugin is available from the plugins menu, but cores when selecting "Connect".

Connect status changed: 1 1 0
Connect status changed: 1 2 0
onNewChannelEvent: 1 1 0
New channel: 1 Default Channel
Connect status changed: 1 3 0
New client: CAX1683
warning: Unknown nb_ctl request: 12
warning: The VAD has been replaced by a hack pending a complete rewrite
onNewChannelEvent: 1 2 0
New channel: 2 17510
onNewChannelEvent: 1 3 0
New channel: 3 18011
onNewChannelEvent: 1 4 0
New channel: 4 18012
onNewChannelEvent: 1 5 0
New channel: 5 18010
onNewChannelEvent: 1 6 0
New channel: 6 12280
onNewChannelEvent: 1 7 0
New channel: 7 12270
onNewChannelEvent: 1 8 0
New channel: 8 16010
onNewChannelEvent: 1 6301 0
New channel: 6301 17010
Connect status changed: 1 4 0
*** buffer overflow detected ***: ./X-Plane-x86_64 terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x73f1f)[0x7f647c6fff1f]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7f647c79782c]
/lib/x86_64-linux-gnu/libc.so.6(+0x10a6f0)[0x7f647c7966f0]
/home/martin/X-Plane10/Resources/plugins/PilotEdge/64/lin.xpl(+0x10fd9)[0x7f64576f5fd9]
/home/martin/X-Plane10/Resources/plugins/PilotEdge/64/lin.xpl(+0x1302c)[0x7f64576f802c]
/home/martin/X-Plane10/Resources/plugins/PilotEdge/64/lin.xpl(+0x13ff0)[0x7f64576f8ff0]
/home/martin/X-Plane10/Resources/plugins/XPWidgets_64.so(XPSendMessageToWidget+0x8c)[0x7f6457b7c179]
/home/martin/X-Plane10/Resources/plugins/XPWidgets_64.so(XPSendMessageToWidget+0x152)[0x7f6457b7c23f]
/home/martin/X-Plane10/Resources/plugins/XPWidgets_64.so(+0xcf16)[0x7f6457b75f16]
/home/martin/X-Plane10/Resources/plugins/XPWidgets_64.so(XPSendMessageToWidget+0x8c)[0x7f6457b7c179]
/home/martin/X-Plane10/Resources/plugins/XPWidgets_64.so(+0x144a4)[0x7f6457b7d4a4]
/home/martin/X-Plane10/Resources/plugins/XPLM_64.so(+0x3b83d)[0x7f6457dc883d]
/home/martin/X-Plane10/Resources/plugins/XPLM_64.so(XPLMMouseClickHook+0x35)[0x7f6457dcaad4]
./X-Plane-x86_64[0xc16b08]
./X-Plane-x86_64[0x6a4c5f]
./X-Plane-x86_64[0xe72136]
./X-Plane-x86_64[0xe70580]
./X-Plane-x86_64[0xe706b9]
./X-Plane-x86_64[0x114bb6c]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f647c6adec5]
./X-Plane-x86_64[0x4104a5]

martin@ubuntu64:~/X-Plane10$ ldd Resources/plugins/PilotEdge/64/lin.xpl
linux-vdso.so.1 => (0x00007fffa8f90000)
libGL.so.1 => /usr/lib/nvidia-340/libGL.so.1 (0x00007fafe61d5000)
libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1 (0x00007fafe5f67000)
libpng12.so.0 => /lib/x86_64-linux-gnu/libpng12.so.0 (0x00007fafe5d40000)
libts3client_linux_amd64.so => Resources/plugins/PilotEdge/64/libts3client_linux_amd64.so (0x00007fafe5790000)
libnvidia-tls.so.340.29 => /usr/lib/nvidia-340/tls/libnvidia-tls.so.340.29 (0x00007fafe558d000)
libnvidia-glcore.so.340.29 => /usr/lib/nvidia-340/libnvidia-glcore.so.340.29 (0x00007fafe2979000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007fafe2644000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007fafe2432000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fafe206b000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fafe1e67000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fafe1b63000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fafe185c000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fafe1646000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fafe142d000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fafe1224000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fafe1006000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007fafe0de7000)
/lib64/ld-linux-x86-64.so.2 (0x00007fafe67b5000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007fafe0be2000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007fafe09dc000)
martin@ubuntu64:~/X-Plane10$

Starting up: PilotEdge client, V1.1.1
initVoice with device alsa_output.pci-0000_01_07.0.analog-stereo, returned 0
PilotEdge initialized
Entered deferred startup
completed deferred startup
Setting up connection details...
Checking for slaves...
Checking for server file...
Checking for voice file...
About to connect...
Connected to PilotEdge Server

On 32-bit the PE client is unavailable:
dlerror:/home/martin/X-Plane10/Resources/plugins/PilotEdge/lin.xpl: undefined symbol: __stack_chk_fail_local

What call sign are you connecting with? What happens if you try a shorter call sign (no more than 5 characters)?

I have also had issues using a keyboard ONLY. Pressing the enter key causes a loop/hang that last for a few seconds. ATC can't hear you during the loop. However, mapping a physical switch to "contact ACT" seems to fix the issue.

Thanks for the suggestion. I tried with the following callsigns:

CAX1683 (cores on connect)
N8816A (cores on connect)
N8816 (successfully connects)

However, CAX1683 and N8816A are valid callsigns and I have had no issues with the Windows client using these.

This has been the same issue on some Macs, callsigns longer than 5 chars are causing dumps. I can't replicate it, though, even with the latest OSX and X-Plane (a configuration which was giving people fits).