VSCodium from Flatpak + Rust-Analyzer extension = Broken?

On a totally fresh install of VSCodium using Flatpak in Pop_OS!, I get an error on first installing the rust-analyzer plugin, pretty much identical to the error that @brianbreniser sees here: Rust-analyzer failed to load workspace (Fedora 36/VSCodium) (Final error seems to be rustc -vV never executed). Many debugging steps already done

rust-analyzer failed to load workspace: Failed to read Cargo metadata from Cargo.toml file /home/.../workspace/rust/guessing_game/Cargo.toml, Some(Version { major: 1, minor: 65, patch: 0 }): Failed to run "/home/.../.cargo/bin/cargo" "metadata" "--format-version" "1" "--manifest-path" "/home/.../workspace/rust/guessing_game/Cargo.toml" "--filter-platform" "x86_64-unknown-linux-gnu": cargo metadata exited with an error: error: could not execute process rustc -vV (never executed)
Caused by:
No such file or directory (os error 2)
Click to reload.

Does anyone have ideas as to why that might be? I assume it has to do with how Flatpaks are installed and the permissions/environment that is given to the executables that are installed for an extension, but I'm not especially skilled at pinpointing that kind of thing. If anyone has any direction to provide, that would be much appreciated.

OS: Pop!_OS 22.04 LTS
VSCodium information:
Version: 1.73.1
Release: 22314
Commit: 14f2d26367b7e8f03ff2352516ba27d6302dd7b1
Date: 2022-11-10T18:19:13.052Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
OS: Linux x64 6.0.6-76060006-generic
Sandboxed: No

Have you tried playing with flatpak override and the sandbox permissions?


This fixed it for me:

flatpak --user override com.vscodium.codium  --env=PATH=/app/bin:/usr/bin:/home/$USER/.cargo/bin

Found here.

Thanks this is perfect! I didn't find that issue while searching around. Thanks!

You were absolutely right, I'm not super familiar with flatpak functionality, and @willswats specified the exact override command that needed to be run.

1 Like