LuaLS / LuaLS/lua-language-server

Encounter "version `GLIBC_2.29' not found" when launching lua-language-server

Open
#2,923 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
4.4k
Forks
442
PR merge metrics
No merged PRs in 30d

Description

### How are you using the lua-language-server?

Visual Studio Code Extension (sumneko.lua)

### Which OS are you using?

Linux

### What is the issue affecting?

Other

### Expected Behaviour

`lua-language-server` should run without errors.

### Actual Behaviour

After starting language server, there are errors in the `Output` View of VS Code.
```
/home/user/.vscode-server/extensions/sumneko.lua-3.12.0-linux-x64/server/bin/lua-language-server: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by /home/user/.vscode-server/extensions/sumneko.lua-3.12.0-linux-x64/server/bin/lua-language-server)
```

### Reproduction steps

1. In VS Code, use `Command Palette` to run `Lua: (debug) Start Language Server`.
2. Navigate to `Output` View of VS Code.
3. See error
```text
[Error - 11:44:03 AM] Server initialization failed.
Message: write EPIPE
Code: -32099
[Error - 11:44:03 AM] Lua client: couldn't create connection to server.
Message: write EPIPE
Code: -32099
[Error - 11:44:03 AM] Restarting server failed
Message: write EPIPE
Code: -32099
[Error - 11:44:03 AM] The Lua server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
/home/user/.vscode-server/extensions/sumneko.lua-3.12.0-linux-x64/server/bin/lua-language-server: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by /home/user/.vscode-server/extensions/sumneko.lua-3.12.0-linux-x64/server/bin/lua-language-server)
/home/user/.vscode-server/extensions/sumneko.lua-3.12.0-linux-x64/server/bin/lua-language-server: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /home/user/.vscode-server/extensions/sumneko.lua-3.12.0-linux-x64/server/bin/lua-language-server)
[Error - 11:44:03 AM] Server process exited with code 1.
```

### Additional Notes

VS Code runs on Windows and remote to Ubuntu.
```
Version: 1.95.1 (system setup)
Commit: 65edc4939843c90c34d61f4ce11704f09d3e5cb6
Date: 2024-10-31T05:14:54.222Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045
```
```
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
```
```
Name: Lua
Id: sumneko.lua
Description: Lua Language Server coded by Lua
Version: 3.12.0
Publisher: sumneko
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=sumneko.lua
```

### Log File

No `log` folder under the path which is mentioned in the wiki page.
```
$ ls ~/.vscode-server/extensions/sumneko.lua-3.12.0-linux-x64/server/
bin changelog.md debugger.lua LICENSE locale main.lua meta script
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure on Ubuntu 18.04 through the VS Code extension, starting with the binary at ~/.vscode-server/extensions/sumneko.lua-3.12.0-linux-x64/server/bin/lua-language-server and the errors in the Output view. Investigate how the language-server binary is packaged for Linux and verify that it launches successfully on the reported environment without the GLIBC_2.29 error.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, lua, ubuntu, vscode
Domain
operating-systems, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.