AppImage: none of the packages launch now (they used to!)

linuxer

Here's the output after making the file executable:
chmod +x file.AppImage
./file.AppImage
nym-connect: error while loading shared libraries: libthai.so.0: cannot open shared object file: No such file or directory

How can i use AppImages again? I prefer Snaps but not all software i need is covered as a Snap (or Flatpak!).
Thanks once more.

EbonJaeger

linuxer do you have libthai installed? It can be installed with sudo eopkg it libthai

linuxer

EbonJaeger

But what is that package? What does it do? I do can see it in the Software Center (not into terminal). I suppose its safe to install and it doesnt effect anything else?

EbonJaeger

linuxer according to the package description, it's:

A set of Thai language support routines aimed to ease developers' tasks to incorporate Thai language support in their applications.

linuxer

EbonJaeger Oh ok, that's a weird one. I wonder why this little language dependency is not installed by default then on the system if its absence prevents AppImage usage OOTB ..

Harvey

linuxer
It does not prevent all AppImages working just applications distributed via AppImage that have libthai as a dependency.

If it is a dependency of the application you are running it should be contain within the AppImage itself, that is the entire point of universal packaging formats. But it is excluded from AppImage generation for reasons no one can explain: https://github.com/AppImageCommunity/pkg2appimage/issues/538

brent

Harvey
starts " If we don*t bundle it, target systems that don't have it installed get an issue
If we bundle it, target systems that have a newer version installed get an issue"

ends with "That just means we have to bundle both libpango and libthai, doesn't it?" dated 8/16.

sounds like it might take a little time.

Harvey that is the entire point of universal packaging formats.

agreed