Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GLIBC_2.34' not found error when opening a flatpak rust project #46

Closed
SeaDve opened this issue Feb 4, 2022 · 7 comments
Closed

GLIBC_2.34' not found error when opening a flatpak rust project #46

SeaDve opened this issue Feb 4, 2022 · 7 comments

Comments

@SeaDve
Copy link
Collaborator

SeaDve commented Feb 4, 2022

VS Code version: 1.63.2 (from flatpak)
Flatpak vscode extension version: 0.0.16
Rust analyzer extension version: 0.2.853
Application Runtime: GNOME 42

Steps to reproduce:

  1. Open rust flatpak project with this and rust-analyzer extension

Rust Analyzer Client Output:

INFO [2/4/2022, 8:55:33 PM]: Using server binary at /home/dave/Projects/noteworthy/.flatpak/rust-analyzer.sh
DEBUG [2/4/2022, 8:55:33 PM]: Checking availability of a binary at /home/dave/Projects/noteworthy/.flatpak/rust-analyzer.sh
DEBUG [2/4/2022, 8:55:33 PM]: /home/dave/Projects/noteworthy/.flatpak/rust-analyzer.sh --version: {
  status: 1,
  signal: null,
  output: [
    null,
    '',
    "rust-analyzer: /usr/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by rust-analyzer)\n"
  ],
  pid: 522,
  stdout: '',
  stderr: "rust-analyzer: /usr/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by rust-analyzer)\n"
}
ERROR [2/4/2022, 8:55:33 PM]: Bootstrap error [Error: Failed to execute /home/dave/Projects/noteworthy/.flatpak/rust-analyzer.sh --version. `config.server.path` or `config.serverPath` has been set explicitly.            Consider removing this config or making a valid server binary available at that path.
	at L0 (/home/dave/.var/app/com.visualstudio.code/data/vscode/extensions/matklad.rust-analyzer-0.2.853/out/main.js:109:3705)
	at runMicrotasks (<anonymous>)
	at processTicksAndRejections (internal/process/task_queues.js:93:5)
	at async F0 (/home/dave/.var/app/com.visualstudio.code/data/vscode/extensions/matklad.rust-analyzer-0.2.853/out/main.js:109:1881)
	at async O0 (/home/dave/.var/app/com.visualstudio.code/data/vscode/extensions/matklad.rust-analyzer-0.2.853/out/main.js:108:3977)
	at async lC (/home/dave/.var/app/com.visualstudio.code/data/vscode/extensions/matklad.rust-analyzer-0.2.853/out/main.js:108:3808)
	at async Promise.all (index 0)]
@bilelmoussaoui
Copy link
Owner

Have you tried removing also the .flatpak folder, close vscode and re-open it and start a new build from scratch?

@SeaDve
Copy link
Collaborator Author

SeaDve commented Feb 4, 2022

Have you tried removing also the .flatpak folder, close vscode and re-open it and start a new build from scratch?

Yeah, I tried it again recently with all files closed

@bilelmoussaoui
Copy link
Owner

Is this a flatpaked vscode ? If so, can you open a build terminal and run r-a there and see how that goes ?

@SeaDve
Copy link
Collaborator Author

SeaDve commented Feb 4, 2022

It outputs the same error rust-analyzer: /usr/lib/x86_64-linux-gnu/libc.so.6: version 'GLIBC_2.34' not found (required by rust-analyzer). It seems to be not an issue then to the extension?

@SeaDve
Copy link
Collaborator Author

SeaDve commented Feb 5, 2022

After removing the path to ~/.cargo/bin/cargo in $PATH, it somehow works properly now.

Closing this I guess, thanks!

@SeaDve SeaDve closed this as completed Feb 5, 2022
@bilelmoussaoui
Copy link
Owner

That is weird, we should probably hardcode the path to make sure we use the SDK rust analyzer

@SeaDve
Copy link
Collaborator Author

SeaDve commented Feb 8, 2022

ill make an issue about that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants