Arch Linux User Repository

For those of you waiting for an update: For the latest 1.94 updates, I indeed managed to tweak stuff a bit according to the updated build process, so that this package builds. But after install, calling codium will just spawn a vscodium process with nothing showing up on the screen. gdb says electron is blocking on a ppoll(). I am completely loss what is happening. I am asking others for help, and also I may wait for the official code package to update (they also use system electron) and see how they do stuff.

--- 2024/10/10 Update ---

Update is online. This helped in updating vscodium.js, otherwise as described above, software will simply not start.

By the way, although electron30 is the officially supported version, by my own experience electron32 also works fine (and vscode upstream is already testing with electron32). If you want to have a try, just change _electron to electron32 and _nodejs to "20.17.0" in PKGBUILD.

Quite a coincidence that just after I pushed the new update, with update to electron30, I see your @coxackie's comment xd. Also, the PKGBUILD is designed in a way so that anyone can change the electron version used (without any guarantees of course). Handy for anyone who only want ONE electron in their system.

I thought electron30 was used already in 1.92...

@Richardn Thank you very much! Works like a charm!

Another thing I noticed: When I try to open a file in vscodium it will open a new, but empty, instance of vscodium. Found out that removing the --unity-launch in the desktop file fixed it, as it is deprecated. It was also removed in the upstream: https://github.com/VSCodium/vscodium/pull/1866

@backbord Fix in place. I also put my understanding of the fix as comments in vscodium.js.

By the way, seems like electron release 29.4.3 is officially online now, so we do not need the dirty fix mentioned above with electron29.

Can we get the proposal https://aur.archlinux.org/packages/vscodium-electron#comment-969003 merged? This is the last thing that is required to fix wayland.

Another day without electron29 update, so you will still be needing the dirty fix mentioned above if you want to build with electron29.

By the way, as a followup to this convo, as now I completely understand the packaging process, I can answer: ripgrep is being depended on because in the usual vscodium package, electron and ripgrep are the only two binary executables present in the compiled files. It is then reasonable for this package to remove both of them and link the system versions of them instead.

I am working on the major v1.90 update, which upgrades to electron 29 and node 20.9.0. However a confusing situation is found: The latest electron 29 version is 29.4.2, however the electron29 in the Arch repo is 29.4.3. This breaks build as the process can't find the source on GitHub for the system electron installed. I have alerted several Arch community managers about this and we are investigating.

--- Update ---

Issue for the electron problem is here

I already updated this repo anyways. By design, you can choose whatever version of system electron to use by modifying the PKGBUILD (of course no one can guarantee that things will run fine).

But, if you choose electron29, due to the issue mentioned above, build will fail. A nasty solution is, modify /usr/lib/electron29/version to be 29.4.2. This can trick the build system into getting electron v29.4.2 source files instead. I did this and the editor appears fine with me so far.

A note from maintainer me: I am still alive and will check and update this package soon. Just that these two weeks I am graduating, moving out from my apartment, preparing US departure, etc., TLDR too busy to do anything else. Sorry for the delay, I will definitely come back to this soon.

Is there any reason why the compiled VSCodium has a different release number than the package indicates? Mine has version 24124, while this package is currently 24102.