#2418 Appimage does not work on Ubuntu 20.04 LTS and many other distributions.

[Hans Deragon]

When pressing the "Download" button on the "Setup required data file" dialog of the AppImage for 2020.3.2, nothing happens, except the error message shown in bold below.

$ ./FlightGear-2020.3.2-x86_64.AppImage
SIMGEAR_TLS_CERT_PATH=/tmp/.mount_FlightLSgRKV/usr/ssl/cacert.pem
LD_LIBRARY_PATH=/tmp/.mount_FlightLSgRKV/usr/lib:
/usr/bin/google-chrome-stable: symbol lookup error: /lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0: undefined symbol: atk_component_scroll_to_point

And thus, my adventure with Flightgear ends here. :(

I am not the only one suffering from this. See: Free and open source flight sim 'FlightGear' has a brand new release on Gaming On Linux.

[James Turner]

Oh dear, seems we're screwing up Chrome when we try to launch it.

[James Turner]

Wild guess: xdg-open (which is how Qt launches the browser) is using fork() and picking up our LD_LIBRARY_PATH which then menas Chomre finds the wrong libatk?

[Megaf]

I reported that on the mail list too.
@jmturner Debian at least, and I believe other distros too have the "link" x-www-browser to open the default browser, wouldn't that fix the issue?

[James Turner]

Actually we fixed this in 2020.3.3, by adjusting how we launch fgfs inside the AppImage. So please check 2020.3.3 and confirm it's working as expected for you.

We don't have direct control over how the browser is launched, it's handled by Qt, but since Qt is widely used to make AppImages, we just had to figure out what we had done incorrectly ourselves. We've understood the issue now after one of my work colleagues explained it to me :)

[Megaf]

Works fine now, thanks!

[Anonymous]

Was asked to close it.