Insync v3.9.7.60031-el9 Requires GLIBC\_2.35 (Breaks RHEL 9 / Rocky 9 Compatibility)

Bugs and issues
1

Hello,

I am experiencing a failure to launch Insync after a recent update to version 3.9.7.60031-el9 on a system running a base compatible with RHEL 9 / Rocky Linux 9.

The issue is that the newly installed package, which is specifically tagged for Enterprise Linux 9 (-el9), appears to have been compiled against or requires a dependency provided by a newer GLIBC version than is available in RHEL 9.

Environment Details:

  • Host OS: Bluefin Linux Stable (recently upgraded to Fedora 43 base)
  • Container OS: Rocky Linux 9 (via Distrobox)
  • Installed Insync Version: 3.9.7.60031-el9 (Installed via the official Insync RHEL 9 repo)
  • GLIBC Version in Container: ldd (GNU libc) 2.34

Error Received on Launch:

/lib64/libc.so.6: version `GLIBC_2.35' not found (required by /usr/lib/insync/libgcc_s.so.1)
Failed to load module: /usr/lib64/gio/modules/libdconfsettings.so
/lib64/libc.so.6: version `GLIBC_2.35' not found (required by /usr/lib/insync/libgcc_s.so.1)
Failed to load module: /usr/lib64/gio/modules/libdconfsettings.so

Request:

Since RHEL 9 and Rocky 9 systems (including all minor releases) are locked to GLIBC 2.34 for the entire life cycle of the release, this package tagged as -el9 is incompatible with the target system.

Could the packaging team please investigate the build process for the RHEL 9 / Rocky 9 RPM to ensure the resulting binaries do not introduce a hard dependency on GLIBC_2.35?

2

:hammer_and_wrench: Update: Confirmed Issue and Temporary Workaround

Hello,

Thank you for looking into this. I’ve performed some further investigation and confirmed the following:

  1. Version Conflict Confirmed: The error only appears in Insync version 3.9.7.60031-el9.
  2. Working Version: I have successfully downgraded the Insync package to the previous version, 3.9.6.60027-el9, which runs correctly on Rocky Linux 9 (GLIBC 2.34).
  3. Conclusion: The version 3.9.7.60031-el9 appears to be an incorrect build for the RHEL 9/Rocky 9 platform, as it introduces the dependency on GLIBC 2.35, which is not available on RHEL 9.

Temporary Workaround

To get my sync running immediately, I have taken the following steps inside my Rocky 9 Distrobox container:

  1. Downgraded the application using sudo dnf downgrade insync-3.9.6.60027.
  2. Excluded the package from future manual DNF updates by adding exclude=insync to /etc/dnf/dnf.conf.

I will keep the application locked on version 3.9.6 for now. Please let us know when a new -el9 package (e.g., 3.9.8-el9) is released that fixes the GLIBC_2.35 dependency.

Thank you.

1 Like
3

I have forwarded this to our engineer for further investigation! Thank you for including all the necessary details. :slight_smile:

4

@wildcat.tominglis Thank you for waiting and apologies for the delay!

Could you please share the output of these two commands:
cat /etc/os-release
dnf list --installed | grep insync

Thank you!

5

Do you want me to do that in the host OS (Bluefin) or the container where Insync is installed (Rocky)?

6

Please do this on the container where Insync is installed. Thank you!

7

cat /etc/os-release

NAME=“Rocky Linux”
VERSION=“9.7 (Blue Onyx)”
ID=“rocky”
ID_LIKE=“rhel centos fedora”
VERSION_ID=“9.7”
PLATFORM_ID=“platform:el9”
PRETTY_NAME=“Rocky Linux 9.7 (Blue Onyx)”
ANSI_COLOR=“0;32”
LOGO=“fedora-logo-icon”
CPE_NAME=“cpe:/o:rocky:rocky:9::baseos”
HOME_URL=“https://rockylinux.org/”
VENDOR_NAME=“RESF”
VENDOR_URL=“https://resf.org/”
BUG_REPORT_URL=“https://bugs.rockylinux.org/”
SUPPORT_END=“2032-05-31”
ROCKY_SUPPORT_PRODUCT=“Rocky-Linux-9”
ROCKY_SUPPORT_PRODUCT_VERSION=“9.7”
REDHAT_SUPPORT_PRODUCT=“Rocky Linux”
REDHAT_SUPPORT_PRODUCT_VERSION=“9.7”

dnf list --installed | grep insync

Nil response

rpm -qa | grep insync

insync-3.9.6.60027-el9.x86_64

8

I’ve forwarded this to our engineers and await their reply!