bug: AppImage of 0.7.1 does not starts in RHEL 9.6

[drrros]

Version: 0.7.1

Describe the Bug

AppImage version does not start at all in RedHat Enterprise Linux 9.6

Steps to Reproduce

Download appimage, chmod and run it.

Screenshots / Logs

[drros@localhost Downloads]$ chmod +x Jan_0.7.1_amd64.AppImage 
[drros@localhost Downloads]$ ./Jan_0.7.1_amd64.AppImage 
Jan: /lib64/libc.so.6: version `GLIBC_2.39' not found (required by Jan)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libcrypto.so.3)
Jan: /lib64/libm.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libgdk-3.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libgdk-3.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libpango-1.0.so.0)
Jan: /lib64/libm.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libcairo.so.2)
Jan: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libcairo.so.2)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libcairo.so.2)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libglib-2.0.so.0)
Jan: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libwebkit2gtk-4.1.so.0)
Jan: /lib64/libm.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libwebkit2gtk-4.1.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libwebkit2gtk-4.1.so.0)
Jan: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libwebkit2gtk-4.1.so.0)
Jan: /lib64/libm.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libgtk-3.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libgtk-3.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libsoup-3.0.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libgio-2.0.so.0)
Jan: /lib64/libm.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libjavascriptcoregtk-4.1.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libjavascriptcoregtk-4.1.so.0)
Jan: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libjavascriptcoregtk-4.1.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libxkbcommon.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libXcursor.so.1)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libicui18n.so.74)
Jan: /lib64/libm.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libicui18n.so.74)
Jan: /lib64/libc.so.6: version `GLIBC_2.35' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libsystemd.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libsystemd.so.0)
Jan: /lib64/libm.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libicuuc.so.74)
Jan: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libicuuc.so.74)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libicuuc.so.74)
Jan: /lib64/libm.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libxml2.so.2)
Jan: /lib64/libm.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libsqlite3.so.0)
Jan: /lib64/libm.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libxslt.so.1)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libxslt.so.1)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libgcrypt.so.20)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libgstreamer-1.0.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libtasn1.so.6)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libwayland-server.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libatk-bridge-2.0.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libgssapi_krb5.so.2)
Jan: /lib64/libc.so.6: version `GLIBC_2.36' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libmount.so.1)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libmount.so.1)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libselinux.so.1)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libcap.so.2)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libdw.so.1)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/liborc-0.4.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libdbus-1.so.3)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libkrb5.so.3)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libk5crypto.so.3)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libkrb5support.so.0)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libblkid.so.1)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libelf.so.1)
Jan: /lib64/libc.so.6: version `GLIBC_2.38' not found (required by /tmp/.mount_Jan_0.lFOflB/usr/lib/libudev.so.1)

Operating System

• MacOS
• Windows
• Linux
  OS details:

[drros@localhost Downloads]$ cat /etc/os-release 
NAME="Red Hat Enterprise Linux"
VERSION="9.6 (Plow)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="9.6"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux 9.6 (Plow)"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9"
BUG_REPORT_URL="https://issues.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_BUGZILLA_PRODUCT_VERSION=9.6
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.6"
[drros@localhost Downloads]$ uname -a
Linux localhost.localdomain 5.14.0-570.35.1.el9_6.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Aug 9 04:12:43 EDT 2025 x86_64 x86_64 x86_64 GNU/Linux

[github-actions]

Found 2 possible duplicate issues:

1. https://github.com/jan-ai/jan/issues/5549
2. https://github.com/jan-ai/jan/issues/1187

[CotonDeCoolear]

The same issue occurs on Debian 12. It began happening with 0.7.0.

[Minh141120]

Hey,
We were encountering a couple of similar issues across different Linux distributions. We're currently working to address this through a Flatpak build, which will make Jan work reliably across Ubuntu, Debian, RHEL, and others.

The Flatpak submission is still in progress, but we’re doing our best to get it published soon.
In the meantime, you can try building Jan from source on your system by installing the following prerequisites first:

Node.js ≥ 20.0.0  
Yarn ≥ 1.22.0  
Make ≥ 3.81  
Rust (for Tauri)

Then clone the repo and run:

make build

This will generate the target file you can run directly on your machine.

Alternatively, you can upgrade your distro (for example, to Ubuntu 24.04 or newer), that will also resolve the GLIBC version issue.

Thanks a lot for your patience while we work on better cross-distro packaging 🙏

[github-roushan]

@drrros . can you provide the output for

ldd --version.

[github-roushan]

@drrros .
Basically it means is that you are using an older version of gcc libraries and jan wants a new one (2.38) for some or better.

Do this to get glibc 2.39

cd /tmp
wget https://ftp.gnu.org/gnu/libc/glibc-2.39.tar.gz
tar -xzf glibc-2.39.tar.gz
cd glibc-2.39
mkdir build && cd build
../configure --prefix=/opt/glibc-2.39
make -j$(nproc)
sudo make install

then run jan like this

/opt/glibc-2.39/lib/ld-linux-x86-64.so.2 \
  --library-path /opt/glibc-2.39/lib ./Jan_0.7.1_amd64.AppImage

or update rhel to newer version (offcourse with glibc 2.38+)

[mruderman]

I am also experiencing issues with the 0.7.1 AppImage on Pop!_OS, but I am seeing a different error. Instead of a GLIBC error (which others in this thread are reporting), my system reports that the file is not a valid squashfs image.

I have done a detailed analysis, and it appears the .squashfs section is missing from the ELF executable, which would explain this failure. This suggests the AppImage may be fundamentally malformed. Here are my detailed findings:

---

Troubleshooting Details

Multiple attempts to run or extract the AppImage have failed. The core issue seems to be that the AppImage is missing its squashfs filesystem.

1. Running with APPIMAGE_EXTRACT_AND_RUN:
   • Command:

     APPIMAGE_EXTRACT_AND_RUN=1 ./Jan_0.7.1_amd64.AppImage

   • Output:

     This doesn't look like a squashfs image. Failed to open squashfs image
     

2. Extracting with --appimage-extract:
   • Command:

     ./Jan_0.7.1_amd64.AppImage --appimage-extract

   • Output:

     This doesn't look like a squashfs image. Failed to open squashfs image
     

3. File Type Check:
   • The file is identified as a valid ELF executable, as expected for a Type 2 AppImage.
   • Command:

     file ./Jan_0.7.1_amd64.AppImage

   • Output:

     Jan_0.7.1_amd64.AppImage: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), static-pie linked...
     

4. ELF Section Header Analysis:
   • An inspection of the executable's section headers reveals that the .squashfs section is missing, which confirms why all attempts to mount or extract the filesystem are failing.
   • Command:

     readelf -S ./Jan_0.7.1_amd64.AppImage

   • Result: The output lists various sections (.appimage, .text, .data, etc.) but no .squashfs section is present.

NOTE: This bug report generated with the assistance of Gemini 2.5 Pro