Vscodium: Command not found: codium

Created on 11 Jun 2019  路  7Comments  路  Source: VSCodium/vscodium

Describe the bug
After the update to 1.35 and the new vscodium-bin package, I can no longer launch vscodium. Typing vscodium or codium into my terminal gives me the error fish: Unknown command vscodium or fish: Unknown command codium.

Please confirm that this problem is VSCodium-specific

  • [ Yes ] This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

  • [ Yes ] I checked the Docs page and my issue is not mentioned there.

It is a fairly recent issue. I noticed that the latest comment from the vscodium-bin AUR page includes "Version 1.35.0 of VSCodium has introduced some breaking changes that are not accommodated in this release. The binary has been renamed to "codium", so "vscodium-bin.desktop" and the symlinks created in the PKGBUILD must be updated to use the new binary." However, I was not able to use codium anyway

To Reproduce
Steps to reproduce the behavior:

  1. Install VSCodium with yay -S vscodium-bin
  2. Enter codium or vscodium into the terminal (doesn't matter if using fish or zsh).

Expected behavior
I expect that an instance of VSCodium would start.

Screenshots
Unnecessary.

Desktop (please complete the following information):

  • OS: Arch Linux 4.19 LTS
  • Architecture: x86-64
  • Version: 1.35.0-1

Additional context
Previously, I had the version of VSCodium where I could launch it with vscodium. When I installed the new version, I reinstalled my computer. I then could not launch it with vscodium or codium.

* Solution *
I was able to launch VSCodium only by going into the /usr/share/vscodium-bin folder and then manually executing codium, e.g. ./codium.

bug

Most helpful comment

Did you try this one?

Screenshot 2019-06-11 at 08 29 22

Shell command 'codium' successfully installed in PATH.

~> which codium
/usr/local/bin/codium

~> codium -v
1.35.0
553cfb2c2205db5f15f3ee8395bbd5cf066d357d
x64

Verify your binary path after that. It was tested in Mac but It should behave similar in Linux.

All 7 comments

Did you try this one?

Screenshot 2019-06-11 at 08 29 22

Shell command 'codium' successfully installed in PATH.

~> which codium
/usr/local/bin/codium

~> codium -v
1.35.0
553cfb2c2205db5f15f3ee8395bbd5cf066d357d
x64

Verify your binary path after that. It was tested in Mac but It should behave similar in Linux.

As @joseluisq has said -- I believe you need to run the "Install 'codium' command in PATH" command inside VSCodium to get it working.

I have tested in __Arch Linux__ and it works after the update.

~> vscodium -v
1.34.0
a622c65b2c713c890fcf4fbf07cf34049d5fe758
x64

~> yay -Sy vscodium-bin
# [Aur: 1]  vscodium-bin-1.35.0-2 ....

~> vscodium -v
1.35.0
553cfb2c2205db5f15f3ee8395bbd5cf066d357d
x64

~> codium -v
1.35.0
553cfb2c2205db5f15f3ee8395bbd5cf066d357d
x64

~> which codium
/usr/bin/codium

After updating to 1.35.0-2, the codium executable is now on my PATH. I can now call it normally. Thank you.

command option to enable CLI doesn't exist anymore in current version.

@brodock are you using the flatpak version? I couldn't find the command in the flatpak but then updated to the "native" version and now I can use codium to open up a project folder

Yes, that was flatpak. I've learned that there are a lot of quirks when running in flatpak, so I assume the lack is due to that.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

daniel-molina picture daniel-molina  路  78Comments

apollolux picture apollolux  路  35Comments

gabeeg picture gabeeg  路  19Comments

JL2210 picture JL2210  路  55Comments

ganapativs picture ganapativs  路  29Comments