Error When Running an AppImage on Arch WSL

I have **Arch WSL2** set up on my **Windows 11** machine and try to run an application named [Avogadro](https://two.avogadro.cc/index.html "Avogadro") by using *AppImage* method without [FUSE](https://github.com/AppImage/AppImageKit/wiki/FUSE "FUSE") package, in which you extract your *AppImage* file with --appimage-extract option and run it by ./AppRun. At first I had this output:

/home/bbk/squashfs-root/usr/bin/avogadro2: error while loading shared libraries: libOpenGL.so.0: cannot open shared object file: No such file or directory

Given the output, I found out there is a missing file *libOpenGL.so.0* and installed the package *libglvnd* that contains the file, then ran ./AppRun again. This time I had something like:

...error while loading shared libraries: libfontconfig.so.1: cannot open shared object file: No such file or directory

Similar to what I had previously, so I installed *fontconfig* package and proceeded with running the application again. However, a small notification window popped up on my screen with empty tiny squares all over in place of supposed text areas with a title that says *"Install Python (archlinux)"* and output in the console:

Avogadroapp version:  1.100.0
Avogadrolibs version:  1.100.0
Qt version:  6.8.1
qt.core.qobject.connect: QObject::connect(QObject, Unknown): invalid nullptr parameter
qt.tlsbackend.ossl: Failed to load libssl/libcrypto.
SSL version:  ""
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
Using locale:  "en_US"
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslSocket
qt.network.ssl: The backend named "cert-only" does not support TLS
qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS initialization failed

After installing *python* package and re-running the application, I get the following output with the application's GUI with the same empty boxes:

Avogadroapp version:  1.100.0
Avogadrolibs version:  1.100.0
Qt version:  6.8.1
qt.core.qobject.connect: QObject::connect(QObject, Unknown): invalid nullptr parameter
qt.tlsbackend.ossl: Failed to load libssl/libcrypto.
SSL version:  ""
qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
Using locale:  "en_US"
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
 registering GPL plugins
qt.network.ssl: The backend "cert-only" does not support QSslSocket
qt.network.ssl: The backend named "cert-only" does not support TLS
qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS initialization failed
OBEnergy: method:  MMFF94
OBEnergy: method:  UFF
OBEnergy: method:  GAFF
"/home/bbk/squashfs-root/usr/bin/obabel"  found:  "/home/bbk/squashfs-root/usr/bin/obabel: Open Babel 3.1.1 -- Jan 21 2025 -- 17:50:29"
Python interpreter "/opt/hostedtoolcache/Python/3.11.11/x64/bin/python3" does not exist trying "python" in your path. Please set a path to the python interpreter.
qt.network.ssl: The backend "cert-only" does not support QSslKey
qt.network.ssl: Active TLS backend does not support key creation
qt.network.ssl: The backend "cert-only" does not support QSslSocket
qt.network.ssl: The backend named "cert-only" does not support TLS
qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS initialization failed
Python interpreter "/opt/hostedtoolcache/Python/3.11.11/x64/bin/python3" does not exist trying "python" in your path. Please set a path to the python interpreter.
OBEnergy: method:  MMFF94
Open Babel formats ready:  145
Setting default format to cjson.

How can I move on from here as I have no idea how to interpret those output messages. **NOTE:** I solved the empty box issue by installing font packages *ttf-dejavu* and *ttf-liberation*. The application GUI seems to be working fine for now, and I will try to update this post as soon as I can sort out, if possible, warnings seen in the output.