Match both the architecture and the runtime
- uname -m
- An x86_64 result matches the x86_64 Linux asset. An aarch64 result matches the 64-bit ARM asset. If your result differs, check the release for an explicit match.
- getconf GNU_LIBC_VERSION
- On a glibc system this prints a version. The build 130 AppImages require glibc 2.39 or newer. If your system uses a different C library, this release note does not establish compatibility.
- AppImage or tar.gz
- The AppImage bundles application libraries subject to the runtime requirement above. The tar.gz build expects host libraries including Qt 6. A missing-library error from that build identifies a dependency to investigate.
Launch the AppImage from its folder
Open a terminal in the folder containing your downloaded AppImage. These commands use the standard x86_64 filename from build 130. Substitute your actual filename on both lines, including any aarch64 or -pgo label.
chmod u+x ./lichii-linux-x86_64.AppImage
./lichii-linux-x86_64.AppImageThe first command grants execute permission to the owner of this file. The second runs it and leaves any startup message in the terminal. In a graphical file manager you can set the same permission in the file’s properties.
Launch the tar.gz build with system libraries
In the download folder, list the contents first and identify the lichii executable. These commands assume the standard x86_64 archive lists lichii at its top level. Use a fresh destination folder and adjust the filename and executable path if your tag differs.
tar -tzf lichii-linux-x86_64.tar.gz
mkdir lichii-build-130
tar -xzf lichii-linux-x86_64.tar.gz -C lichii-build-130
cd lichii-build-130
./lichiiRun it as your normal desktop user. If the terminal names a missing Qt 6 or other shared library, use that exact name when looking up the required runtime package for your distribution.
Follow the first terminal error
- Permission denied
- Check the execute bit on this file. If it is executable but stored on a volume mounted noexec, move it to a location where your account can run applications.
- Exec format error
- Compare uname -m with the filename and confirm you downloaded a Linux build. Changing permissions cannot translate a binary built for another CPU.
- FUSE or GLIBC error
- For a FUSE message, check AppImage’s instructions for your distribution. For a missing GLIBC version, compare the required number with your host version before trying another package.
- Missing shared library
- If you chose tar.gz, extract the whole directory and record the library name exactly. Look it up in your distribution’s package documentation. A matching filename from a random download is a poor substitute for a compatible package.
Linux FAQ
The AppImage is executable but returns Exec format error. What should I check?
Run uname -m and compare the result with the filename. For example, an aarch64 host needs the Linux aarch64 build. Granting execute permission again will not fix an architecture mismatch.
Can I use the tar.gz as a workaround for an old glibc?
The tar.gz uses host libraries such as Qt 6, so switching formats does not guarantee compatibility with an older distribution. Start the extracted lichii binary in a terminal and read the first missing library or version it names.
After I type the AppImage filename, my shell says command not found. Is it missing?
In the folder where you saved it, list the files and check the spelling and case. Run the executable with ./ before its filename so the shell looks in the current directory.