You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
v0.29.0 doesn't work on operating systems with older glibc (Ubuntu 20.04, Debian Bullseye, etc.) #1085
I can't seem to reproduce this issue. Do you mind sending the output of Output (in the bottom panel) > XML Support ? It might contain some errors or other clues as to what's happening.
Does this happen with all XML files or just a specific one?
Hi — thanks for the pointer. Here’s exactly what I saw when the extension starts:
/.vscode-server/extensions/redhat.vscode-xml-0.29.0-linux-x64/server/lemminx-linux: \
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found \
(required by .../lemminx-linux)
/.vscode-server/extensions/redhat.vscode-xml-0.29.0-linux-x64/server/lemminx-linux: \
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found \
(required by .../lemminx-linux)
At the time I was on Debian 11 “Bullseye” (GLIBC 2.31). After upgrading my environment to Debian 12 “Bookworm” (GLIBC 2.36), the XML formatting is back to normal.
I’ll go ahead and close this since it’s fixed on my end—thanks again!
No problem! Thanks for reporting. Unfortunately, this is an expected issue, and we don't have a way around it in order to support older operating systems.
Here's the change that caused the issue: #1081 . GitHub Actions dropped support for older versions of Ubuntu. When we build on the newer Ubuntu, the built binary it links to the newer glibc, which is not backwards compatible.
changed the title [-]"There is no formatter for 'xml' files installed" when using v0.29.0[/-][+]v0.29.0 doesn't work on operating systems with older glibc (Ubuntu 20.04, Debian Bullseye, etc.)[/+]on May 12, 2025
@pikadun could you please open a separate issue? Are you on Ubuntu or macOS? The extension seems to be the Linux one, but the version of VS Code seems to be the macOS Apple Silicon one.
@Schwuuuuup this is not a Red Hat product, we can only offer best-effort maintenance, with the extremely limited resources affected to this project.
You should still be able to use the extension on any linux version, provided you run the language server with a Java runtime.
"XML Language Support" is a Red Hat-led project, not a product that Red Hat provides as part of a subscription (in which case you'd get LTS kind of support)
Activity
datho7561 commentedon May 12, 2025
I can't seem to reproduce this issue. Do you mind sending the output of Output (in the bottom panel) > XML Support ? It might contain some errors or other clues as to what's happening.
Does this happen with all XML files or just a specific one?
gustitammam commentedon May 12, 2025
Hi — thanks for the pointer. Here’s exactly what I saw when the extension starts:
At the time I was on Debian 11 “Bullseye” (GLIBC 2.31). After upgrading my environment to Debian 12 “Bookworm” (GLIBC 2.36), the XML formatting is back to normal.
I’ll go ahead and close this since it’s fixed on my end—thanks again!
datho7561 commentedon May 12, 2025
No problem! Thanks for reporting. Unfortunately, this is an expected issue, and we don't have a way around it in order to support older operating systems.
datho7561 commentedon May 12, 2025
Here's the change that caused the issue: #1081 . GitHub Actions dropped support for older versions of Ubuntu. When we build on the newer Ubuntu, the built binary it links to the newer glibc, which is not backwards compatible.
See also #916 (comment)
[-]"There is no formatter for 'xml' files installed" when using v0.29.0[/-][+]v0.29.0 doesn't work on operating systems with older glibc (Ubuntu 20.04, Debian Bullseye, etc.)[/+]pikadun commentedon May 13, 2025
@datho7561
I got another error on Ubuntu 24.04.2
Identifier: redhat.vscode-xml
Version: 0.29.0
Version: 1.100.0 (Universal)
Commit: 19e0f9e681ecb8e5c09d8784acaa601316ca4571
Date: 2025-05-07T12:48:53.763Z
Electron: 34.5.1
ElectronBuildId: 11369351
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 23.6.0
datho7561 commentedon May 13, 2025
@pikadun could you please open a separate issue? Are you on Ubuntu or macOS? The extension seems to be the Linux one, but the version of VS Code seems to be the macOS Apple Silicon one.
kczx3 commentedon May 22, 2025
We're on RHEL8 and just started being impacted by this. Downgraded as well. Guess I'm version locked until our development server is upgraded to RHEL9
Ma202010 commentedon Jan 1, 2026
关闭
Schwuuuuup commentedon Sep 10, 2026
This is still an ISSUE on RHEL8.. I thought this was a Red Hat project. I'm a bit disappointed that this does not respect LTS strategies.
fbricon commentedon Sep 10, 2026
@Schwuuuuup this is not a Red Hat product, we can only offer best-effort maintenance, with the extremely limited resources affected to this project.
You should still be able to use the extension on any linux version, provided you run the language server with a Java runtime.
Schwuuuuup commentedon Sep 10, 2026
Well then my English proficiency is not as good as I thought
fbricon commentedon Sep 10, 2026
"XML Language Support" is a Red Hat-led project, not a product that Red Hat provides as part of a subscription (in which case you'd get LTS kind of support)