-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Doesn't work on Flatpak: "Rust-analyzer failed to load workspace: Failed to read Cargo metadata from Cargo.toml file" #13926
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
Comments
Sounds like it couldn't run that. How did you install Rust, and do And please provide the information requested in the issue template: rust-analyzer version: (eg. output of "rust-analyzer: Show RA Version" command, accessible in VSCode via Ctrl/⌘+Shift+P) rustc version: (eg. output of relevant settings: (eg. client settings, or environment variables like |
rust-analyzer version: 0.3.1361-standalone As far as I can remember, I installed Rust using a command provided on website, it just worked since then, I updated it couple times and didn't have any problems.
So here what I got:
|
Did you run those from a terminal, or from the Code terminal? Does anything change if you run Code from a terminal? |
Ah, do you mean that I have to launch Code from the terminal? Well I ran those using terminal inside Code. |
We just run |
I tried, it returned nothing. I'm confused. I've compiled my programs many times succesfully and never had an issue. |
I think we have an issue or two about the Flatpak version. That seems like it could cause problems. |
Thanks, I will reinstall VSCodium asap and tell you about results |
Installing VSCodium from .deb repo resolved the problem. Probably an issue is about something with Flatpak |
Sorry, I know that similar issues were opened several times (#3118, #3885), but I have no idea about what causes my problem.
This is what notification from rust-analyzer looks like:
This is just an example, for showcasing I made a repo for that project, you can have a look on Cargo.toml and any other files here.
The text was updated successfully, but these errors were encountered: