Package Details: vscodium-electron 1.99.32562-1

Git Clone URL: https://aur.archlinux.org/vscodium-electron.git (read-only, click to copy)
Package Base: vscodium-electron
Description: VS Code without MS branding/telemetry/licensing. - System-wide Electron edition
Upstream URL: https://github.com/VSCodium/vscodium
Keywords: code codium electron system vscode vscodium wayland
Licenses: MIT
Conflicts: codium, vscodium, vscodium-bin, vscodium-git
Provides: codium, vscodium
Submitter: m00nw4tch3r
Maintainer: Richardn
Last Packager: Richardn
Votes: 10
Popularity: 1.18
First Submitted: 2022-04-10 18:19 (UTC)
Last Updated: 2025-04-19 02:15 (UTC)

Latest Comments

1 2 3 4 5 6 7 Next › Last »

Damgaldor commented on 2025-04-19 20:20 (UTC) (edited on 2025-04-19 20:20 (UTC) by Damgaldor)

This patch/version of Codium breaks saving files with elevated privileges: Unable to save 'file.desktop': Command failed: cd "/usr/share/applications"; "/usr/bin/pkexec" --disable-internal-agent /bin/bash -c "echo SUDOPROMPT; \"/usr/lib/electron34/bin/codium\" --file-write \"/home/damglador/.config/VSCodium/code-elevated-8Fx763Uj\"" /bin/bash: line 1: /usr/lib/electron34/bin/codium: No such file or directory

Richardn commented on 2025-01-30 16:15 (UTC)

@xinayder This is likely caused by certain behaviors of your AUR helper I think. I know some of those would cache the dependency requirements they see from the original repo, so changes you do to PKGBUILD yourself might not be reflected.

xinayder commented on 2025-01-28 19:44 (UTC)

@Richardn that's interesting. I tried editing the PKGBUILD to use the latest electron, and not electron32, and it still falls back to electron32.

Richardn commented on 2025-01-13 15:40 (UTC) (edited on 2025-01-13 15:43 (UTC) by Richardn)

@xinayder No for two reasons.

  1. VSCodium, or to say the VSCode core might not be depending on the latest electron version. Actually it for the most of the time depends on older versions, and using newer electron actually can break VSCodium.
  2. We aim to use system-wide electron here to reduce bloat (in addition to enhanced performance), so users are free to choose whichever electron they already have on their system. The scripts of this package are designed for this purpose, where anyone can change the _electron (and _nodejs) in the beginning of PKGBUILD. For myself, I have only electron32 installed on my system, and both Discord and VSCodium depend on that.

xinayder commented on 2025-01-08 22:56 (UTC) (edited on 2025-01-08 22:56 (UTC) by xinayder)

Shouldn't this package use simply electron and not use a hardcoded version?

Richardn commented on 2025-01-08 17:01 (UTC)

@sparr This is strange, as I don't have yarn installed on my system and everything builds in a clean chroot environment. FYI, if you look a few lines above in the PKGBUILD, you will find me setting up a local node environment and install yarn, so a system yarn is not required.

Can you try directly makepkg-ing with yarn uninstalled? This may be a problem in yay I'm afraid.

sparr commented on 2025-01-08 13:13 (UTC)

/home/sparr/.cache/yay/vscodium-electron/PKGBUILD: line 115: yarn: command not found

package needs a dependency on yarn

Richardn commented on 2024-10-08 17:00 (UTC) (edited on 2024-10-10 13:55 (UTC) by Richardn)

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.

Richardn commented on 2024-09-10 02:45 (UTC)

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.

1 2 3 4 5 6 7 Next › Last »