google-gemini
Code assist vscode extension v2.57 introduces breaking change (2.56->2.57) related to glibc
What happened?
Updated vscode gemini code assist extension v2.56 to current v2.57 Extension won't connect to server, no server -> no service, doesn't work. Output log:
[Error - 2:23:46 PM] Client Gemini Code Assist: connection to server is erroring.
write EPIPE
Shutting down server.
[Error - 2:23:46 PM] Client Gemini Code Assist: connection to server is erroring.
write EPIPE
[Error - 2:23:46 PM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
at b.shutdown (/home/user/.vscode/extensions/google.geminicodeassist-2.57.0/dist/extension.js:2:9072616)
at b.stop (/home/user/.vscode/extensions/google.geminicodeassist-2.57.0/dist/extension.js:2:9072197)
at b.stop (/home/user/.vscode/extensions/google.geminicodeassist-2.57.0/dist/extension.js:2:9238699)
at b.handleConnectionError (/home/user/.vscode/extensions/google.geminicodeassist-2.57.0/dist/extension.js:2:9078715)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
[Error - 2:23:46 PM] Server initialization failed.
Message: write EPIPE
Code: -32099
[Error - 2:23:46 PM] Gemini Code Assist client: couldn't create connection to server.
Message: write EPIPE
Code: -32099
[Info - 2:23:46 PM] Connection to server got closed. Server will restart.
true
/home/user/.cache/cloud-code/cloudcode_cli/cloudcode_cli/843fe954/cloudcode_cli: /lib64/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /home/user/.cache/cloud-code/cloudcode_cli/cloudcode_cli/843fe954/cloudcode_cli)
What did you expect to happen?
I expected it to function normally
Client information
Client Information
OS: almalinux 9.6 glibc: 2.34 (glibc 2.36 introduces this problematic symbol: GLIBC_ABI_DT_RELR) vscode: 1.105.1 code assist extension: 2.56/2.57Run gemini to enter the interactive CLI, then run the /about command.
> /about
About Gemini CLI
CLI Version 0.12.0
Git Commit 9e7c80f2
Model auto
Sandbox no sandbox
OS linux
Auth Method OAuth
Login information
No response
Anything else we need to know?
No response
I am having the exact same error here:
[Error - 10:55:59 AM] Client Gemini Code Assist: connection to server is erroring. write EPIPE [Error - 10:55:59 AM] Stopping server failed Error: Client is not running and can't be stopped. It's current state is: starting at b.shutdown (/home/user/.vscode/extensions/google.geminicodeassist-2.57.0/dist/webpack:/node_modules/vscode-languageclient/lib/common/client.js:964:19) at b.stop (/home/user/.vscode/extensions/google.geminicodeassist-2.57.0/dist/webpack:/node_modules/vscode-languageclient/lib/common/client.js:935:21) at b.stop (/home/user/.vscode/extensions/google.geminicodeassist-2.57.0/dist/webpack:/node_modules/vscode-languageclient/lib/node/main.js:150:22) at b.handleConnectionError (/home/user/.vscode/extensions/google.geminicodeassist-2.57.0/dist/webpack:/node_modules/vscode-languageclient/lib/common/client.js:1196:18) at processTicksAndRejections (node:internal/process/task_queues:105:5) [Error - 10:55:59 AM] Server initialization failed. Message: write EPIPE Code: -32099 [Error - 10:55:59 AM] Gemini Code Assist client: couldn't create connection to server. Message: write EPIPE Code: -32099 [Error - 10:55:59 AM] The Gemini Code Assist server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information. /home/user/.cache/cloud-code/cloudcode_cli/cloudcode_cli/843fe954/cloudcode_cli: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by /home/user/.cache/cloud-code/cloudcode_cli/cloudcode_cli/843fe954/cloudcode_cli) [Error - 10:55:59 AM] Server process exited with code 1.
Mitigation:
- Go to extension management for Googe Code Assist.
- Turn of Auto Update
- Click the Uninstall DROPDOWN ARROW
- Select Install Specific Version..
- Pick 2.55 (the version that worked for me)
- Restart VS code
Mitigation:
- Go to extension management for Googe Code Assist.
- Turn of Auto Update
- Click the Uninstall DROPDOWN ARROW
- Select Install Specific Version..
- Pick 2.55 (the version that worked for me)
- Restart VS code
Thanks a lot. This works. 2.56 also work for me, but not 2.57.
The issue is that the 2.57 version was built on a newer OS with GLIBC version >=2.36. If your OS has an older version the error happens. You can check your GLIBC version with ldd --version in bash. The easiet solution is to downgrade the plugin to a previous working version, turn off auto-update, and wait for them to fix this.
The issue is that the 2.57 version was built on a newer OS with GLIBC version >=2.36. If your OS has an older version the error happens. You can check your GLIBC version with
ldd --versionin bash. The easiet solution is to downgrade the plugin to a previous working version, turn off auto-update, and wait for them to fix this.
So I am trying to upgrade my Ubuntu 22.04
Some problem here. Here I use Ubuntu 22.04 and I don't have sudo access. I uninstalled 2.57, installed the 2.56 and it works now.
Mitigation:
- Go to extension management for Googe Code Assist.
- Turn of Auto Update
- Click the Uninstall DROPDOWN ARROW
- Select Install Specific Version..
- Pick 2.55 (the version that worked for me)
- Restart VS code
not a issue, you just saved my marriage
Not using gemini-cli, but VS Code extension on a fresh install of Tuxedo OS (based on latest Ubuntu LTS). I had exactly the same issue, and also solved by downgrading to version 2.56.0.
FWIW, I was able to sign in after enabling the insiders update channel (geminicodeassist.updateChannel).
This updated the extension to 2.58.0-insiders.2
I also had to make sure that code assist project (geminicodeassist.project), was set.
My project has 'cloudaicompanion.gemini_code_assist_metrics' and 'cloudaicompanion.cloudaicompanion_all_active_users' google cloud services enabled.
Where does those settings you mentioned happen to go?
On Sun, Nov 9, 2025, 14:42 Dan Thompson @.***> wrote:
dt1900 left a comment (google-gemini/gemini-cli#12657) https://github.com/google-gemini/gemini-cli/issues/12657#issuecomment-3508747789
FWIW, I was able to sign in after enabling the insiders update channel (geminicodeassist.updateChannel).
This updated the extension to 2.58.0-insiders.2
I also had to make sure that code assist project (geminicodeassist.project), was set.
My project has 'cloudaicompanion.gemini_code_assist_metrics' and 'cloudaicompanion.cloudaicompanion_all_active_users' google cloud services enabled.
— Reply to this email directly, view it on GitHub https://github.com/google-gemini/gemini-cli/issues/12657#issuecomment-3508747789, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGAD6WEI6EJYVIS3BXZJKIL336KI3AVCNFSM6AAAAACLLZ6K4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMBYG42DONZYHE . You are receiving this because you authored the thread.Message ID: @.***>
Mitigation:
- Go to extension management for Googe Code Assist.
- Turn of Auto Update
- Click the Uninstall DROPDOWN ARROW
- Select Install Specific Version..
- Pick 2.55 (the version that worked for me)
- Restart VS code
this works for v2.56 too
Mitigation:
- Go to extension management for Googe Code Assist.
- Turn of Auto Update
- Click the Uninstall DROPDOWN ARROW
- Select Install Specific Version..
- Pick 2.55 (the version that worked for me)
- Restart VS code
It's magic! Works to me.
This is the case for Pop!_OS's current stable version, since it is based on Ubuntu 22.04.
Mitigation:
- Go to extension management for Googe Code Assist.
- Turn of Auto Update
- Click the Uninstall DROPDOWN ARROW
- Select Install Specific Version..
- Pick 2.55 (the version that worked for me)
- Restart VS code
not a issue, you just saved my marriage
same issue, thx
additional (auto update uncheck)
- uninstall
gemini code assist - auto update disable
- Specific Version(v2.55) install
- restart
Where does those settings you mentioned happen to go? …
This is in the extension settings. Open the extension, click on the gear icon on the right, then click "settings"
Same issue! Ubuntu Jammy LTS + ldd 2.35...
Gemini announced EOL for Ubuntu 22 ?!
lsb_release -a
No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.5 LTS Release: 22.04 Codename: jammy
ldd --version
ldd (Ubuntu GLIBC 2.35-0ubuntu3.11) 2.35 Copyright (C) 2022 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Roland McGrath and Ulrich Drepper.
Mitigation:
- Go to extension management for Googe Code Assist.
- Turn of Auto Update
- Click the Uninstall DROPDOWN ARROW
- Select Install Specific Version..
- Pick 2.55 (the version that worked for me)
- Restart VS code
This works for me thx . I guess the problem is in the latest version of gemini extension v2.57
This was introduced with the GCA VS Code extension version 2.57 and is caused by a change in the language server where we use cgo to link in some native support for tree sitter. As part of this change on Linux the language server in GCA the gnu c runtime dependency requires 2.36 or higher. There are two ways to resolve this while we look for a possible fix for this issue (hopefully requiring a lesser version):
- Upgrade the gnu c runtime version past on the Linux machine in question (recommended), preferably past 2.38 (see below)
- Downgrade the GCA VS Code extension to the 2.56 version
There are two reasons tor recommending the update of the system in question. The first and most significant reason is that any version < 2.38 has some pretty significant vulnerabilities. Therefore I would highly recommend updating these machines through a system update which should take care of the issue with GCA and to do this regardless of whether or not you also downgrade GCA. The second reason is that the 2.57 change that introduced this issue also introduces very significant performance improvements over the previous version.
hardware won't support is upgrade
On Thu, Nov 13, 2025, 11:32 Keith Schaab @.***> wrote:
kschaab left a comment (google-gemini/gemini-cli#12657) https://github.com/google-gemini/gemini-cli/issues/12657#issuecomment-3528651267
This was introduced with the GCA VS Code extension version 2.57 and is caused by a change in the language server where we use cgo to link in some native support for tree sitter. As part of this change on Linux the language server in GCA the gnu c runtime dependency requires 2.36 or higher. There are two ways to resolve this while we look for a possible fix for this issue (hopefully requiring a lesser version):
- Upgrade the gnu c runtime version past on the Linux machine in question (recommended), preferably past 2.38 (see below)
- Downgrade the GCA VS Code extension to the 2.56 version
There are two reasons tor recommending the update of the system in question. The first and most significant reason is that any version < 2.38 has some pretty significant vulnerabilities. Therefore I would highly recommend updating these machines through a system update which should take care of the issue with GCA and to do this regardless of whether or not you also downgrade GCA. The second reason is that the 2.57 change that introduced this issue also introduces very significant performance improvements over the previous version.
— Reply to this email directly, view it on GitHub https://github.com/google-gemini/gemini-cli/issues/12657#issuecomment-3528651267, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGAD6WCBQ3DZRN2TADD7HET34SXA3AVCNFSM6AAAAACLLZ6K4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMRYGY2TCMRWG4 . You are receiving this because you authored the thread.Message ID: @.***>
There are two reasons tor recommending the update of the system in question. The first and most significant reason is that any version < 2.38 has some pretty significant vulnerabilities
What are backports anyway? (before anyone that reads this on up to date systems and panics) -
Debian 11 has ldd (Debian GLIBC 2.31-13+deb11u13) 2.31 and there's no outstanding vulnerabilities. I'm more likely to just switch my team off Gemini. Replacing the C runtime on a still supported infra just to support a VS code extension isn't going to get a lot of traction.
I apologize, it is not my intent to panic people, I was genuinely trying to be helpful. For the CVE I was referencing and your system here is announcement that applies to 2.31-13+deb11u13 being patched, thank you for the information. FYI.