Skip to content
CC Switch WikiUnofficial Community Wiki

`GLIBC_2.35' not found — CC Switch

Quick fix

No confirmed compatible release exists from v3.10.1–v3.16.1. Try v4; if it still fails, report the version and reproduction steps.

Symptom

Section titled “Symptom”
Error output
cc-switch: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by cc-switch)

Cause

Section titled “Cause”

These AppImages depend on GLIBC symbol versions unavailable on the host system. RHEL 8 and Rocky Linux 8 use GLIBC 2.28 and also lack GLIBC_2.29, GLIBC_2.30, GLIBC_2.32, GLIBC_2.33, and GLIBC_2.34 at runtime. RHEL 9 and Rocky Linux 9 use GLIBC 2.34, which still does not satisfy GLIBC_2.35.

Reports cover v3.10.1 through v3.16.1, but neither users nor maintainers confirmed that any v3 release fixed the issue. The RHEL 9 RPM has another packaging compatibility variant: the system repository provides only the webkit2gtk 4.0 ABI, while the RPM requires libwebkit2gtk-4.1.so.0. Older build bases and Flatpak were suggested but not successfully verified in the threads. The maintainer only suggested trying v4 and submitting another report with more information if the issue persists.

Fix

Section titled “Fix”

  1. Do not treat any reported release from v3.10.1–v3.16.1 as confirmed compatible with RHEL 8/9; these threads do not identify a verified working v3 release.

  2. As the maintainer suggested, try the latest v4 release.

  3. If v4 still produces the same error, reopen or submit an issue with the CC Switch version, Linux distribution, GLIBC version, and reproduction steps.

Affected Versions

Section titled “Affected Versions”
Toolcc-switch
Version受影响版本：3.10.1 - 3.16.1
PlatformsLinux

Source Issues

Section titled “Source Issues”

This page is distilled from 3 real issues

FAQ

Section titled “FAQ”
Which CC Switch version should I use with RHEL 8 and GLIBC 2.28?
The existing threads do not confirm that any v3 release works; failures were reported with v3.10.1 and v3.16.1. The maintainer suggests trying v4 and reporting the version and reproduction steps if the issue persists.
Is there an update on this issue?
The RHEL/Rocky Linux 8.x support request remains open. Two other threads were closed without a verified compatibility fix: one was closed after prolonged inactivity, and the other was closed after v4 was released with a recommendation to try the new release.
Can Flatpak or a build based on an older system fix this?
One participant shared a self-compiled Flatpak, and others suggested Ubuntu 20.04, Debian 11, or a similarly old build base to reduce the GLIBC requirement. Neither users nor maintainers confirmed that these approaches fixed the issue.
Section titled “Related problems”
Symlink target not found: .DirIcon broken symlink causes - CC SwitchAppImage install fails due to broken .DirIcon symlink. Fix by converting it to a relative path.2 issues mergeddoes not run on macOS versions other than Monterey: CC Switch installation failureRun `brew update` and retry. If the cask is still locked to Monterey, change the macOS condition to `>= :monterey`.2 issues mergedError 2503: CC Switch MSI Installation Fails on Windows 11Open Command Prompt as an administrator and run msiexec /i with the MSI file path.3 issues merged

This is an unofficial community wiki with no affiliation to the cc-switch authors or the project itself. Its content is compiled from the project's public GitHub issues. This site distributes no software.