GLIBC backward compatibility

Bug Reports
1

Describe the Bug

Backward compatibility with GLIBC has been broken in the newest update:

[2025-07-04 07:21:49] error This machine does not meet Cursor Server’s prerequis
tes, expected either…

  • find GLIBC >= v2.28.0 (but found v2.27.0 instead) for GNU environments
  • find /lib/ld-musl-x86_64.so.1, which is required to run the Cursor Server in
    n musl environments

Steps to Reproduce

Attempt to connect Cursor to AWS EC2 instance

Expected Behavior

Cursor connect and loads file system

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.1 (user setup)
VSCode Version: 1.99.3
Commit: 031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0
Date: 2025-07-03T06:16:02.610Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631

Does this stop you from using Cursor

Yes - Cursor is unusable

3

I am having the same issue. Is there a way to install the last version of Cursor?

4

Same, having the same issue.

5

I had to update my ubuntu after making a snapshot. but the backward compatibility needs fixing. not all legacy systems can be updated. servers should be respected and not be forced to update by a code editor of all things

6

Agreed. For some of us, these are institutional clusters, we can’t upgrade.

7

Hi,

I found 1.1.7 here, and have re-installed it.

1 Like
8

Thank you! Thought I was stuck running 0.50