Package Details: vscodium 1.100.23258-1

Git Clone URL: https://aur.archlinux.org/vscodium.git (read-only, click to copy)
Package Base: vscodium
Description: Free/Libre Open Source Software Binaries of VSCode (git build from latest release).
Upstream URL: https://github.com/VSCodium/vscodium.git
Licenses: MIT
Conflicts: codium, vscodium, vscodium-bin, vscodium-git
Provides: codium, vscodium
Submitter: cedricroijakkers
Maintainer: cedricroijakkers (daiyam)
Last Packager: daiyam
Votes: 79
Popularity: 2.46
First Submitted: 2021-04-10 15:12 (UTC)
Last Updated: 2025-05-15 19:02 (UTC)

Pinned Comments

Latest Comments

1 2 3 4 5 6 .. 12 Next › Last »

anark10n commented on 2025-06-02 10:49 (UTC) (edited on 2025-06-02 10:49 (UTC) by anark10n)

I get this error when attempting to install:

[12:04:30] 'vscode-reh-web-linux-x64-min-ci' errored after 5.83 min
[12:04:30] AbortError: This operation was aborted
    at new DOMException (node:internal/per_context/domexception:53:5)
    at AbortController.abort (node:internal/abort_controller:391:18)
    at Timeout._onTimeout (/home/anark10n/.cache/yay/vscodium/src/vscode/build/lib/fetch.js:47:53)
    at listOnTimeout (node:internal/timers:581:17)
    at process.processTimers (node:internal/timers:519:7)
+++ error_function build
+++ ((  ! BASH_SUBSHELL  ))
++++ gettext 'A failure occurred in %s().'
+++ error 'A failure occurred in %s().' build
+++ local 'mesg=A failure occurred in %s().'
+++ shift
++++ gettext ERROR:
+++ printf '==> ERROR: A failure occurred in %s().\n' build
==> ERROR: A failure occurred in build().
++++ gettext Aborting...
+++ plainerr Aborting...
+++ plain Aborting...
+++ ((  QUIET  ))
+++ local mesg=Aborting...
+++ shift
+++ printf '    Aborting...\n'
    Aborting...
+++ exit 4
+ clean_up
+ local EXIT_CODE=4
+ ((  INFAKEROOT  ))
+ [[ -p '' ]]
+ ((  (EXIT_CODE == E_OK || EXIT_CODE == E_INSTALL_FAILED) && BUILDPKG && CLEANUP  ))
+ remove_deps
+ ((  ! RMDEPS  ))
+ return 0
+ exit 4
 -> error making: vscodium-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
vscodium - exit status 4

LFdev commented on 2025-05-29 18:36 (UTC)

@cedricroijakkers Thank you for maintaining the package. Please add support for vscodium in the URL handler as well, so it is possible to use OAuth out of the box:

$ diff /usr/share/applications/vscodium-uri-handler.desktop ./vscodium-uri-handler.desktop
11c11
< MimeType=x-scheme-handler/vscode;
---
> MimeType=x-scheme-handler/vscode;x-scheme-handler/vscodium;

oech3 commented on 2025-05-06 09:17 (UTC)

Would you depends=(ripgrep);ln -sf /usr/bin/rg /pathto/app/node_modules/@vscode/ripgrep/bin/rg ?

Richardn commented on 2025-04-19 02:11 (UTC)

In PKGBUILD, need to add a line of

# I put it under `rustup default stable`
export CARGO_TARGET_DIR=${srcdir}/${pkgname}/vscode/cli/target

so for users like me who has non-default cargo target directory, the compiled rust binaries will appear in expected locations and the rest of the build script will work.

Honestly I think this is an upstream problem not specifying the target directory explicitly, but here I provide a quick solution for this package anyways.

InspiringSand commented on 2025-04-12 10:00 (UTC)

A few days ago, rustup was added as a dependency: https://aur.archlinux.org/cgit/aur.git/commit/?h=vscodium&id=492c1cbd08d7ee5488b23b1b026734f87ae65865

But that package conflicts with rust (https://archlinux.org/packages/extra/x86_64/rustup/), since it provides rust.

One solution would be to remove rust.

yay -R rust

Updating directly then might not work yet, since your rustc version might be too old:

error: package clap v4.5.4 cannot be built because it requires rustc 1.74 or newer, while the currently active rustc version is 1.69.0
Either upgrade to rustc 1.74 or newer, or use
cargo update -p clap@4.5.4 --precise ver
where ver is the latest version of clap supporting rustc 1.69.0
++++ error_function build

To update it, install rustup explicitly first and then install latest stable:

yay rustup
rustup install stable

Now you can update vscodium. Not sure I'm happy with this change, since it seems like a more complicated dependency.

joern_h commented on 2025-04-10 08:09 (UTC)

I have an improvement to share: Yesterday I encountered a extension, that had me login via web browser and then return the login token back to vscodium, with the vscodium:// url sheme. This could not be resolved.

I had to modify codium-url-handler.desktop and add a new mime type: MimeType=x-scheme-handler/vscode;x-scheme-handler/vscodium;

Please add this change to the next release.

AvidSeeker commented on 2025-04-08 02:22 (UTC)

Version 1.99.02289-1 not building:

+++ [[ 3 == 3 ]]
+++ echo 'Npm install failed too many times'
Npm install failed too many times
+++ exit 1
+ clean_up
+ local EXIT_CODE=1
+ ((  INFAKEROOT  ))
+ [[ -p '' ]]
+ ((  (EXIT_CODE == E_OK || EXIT_CODE == E_INSTALL_FAILED) && BUILDPKG && CLEANUP  ))
+ remove_deps
+ ((  ! RMDEPS  ))
+ return 0
+ exit 1
 -> error making: vscodium-exit status 1
 -> Failed to install the `

bannert commented on 2025-03-17 19:55 (UTC)

The icon is not correctly used on Wayland and instead the Wayland icon is shown in the task bar and the window title bar. Here is a corresponding GitHub issue: https://github.com/VSCodium/vscodium/issues/2212

daviding commented on 2025-01-22 02:54 (UTC) (edited on 2025-01-22 02:59 (UTC) by daviding)

Installation of 1.96.4.25017-1 hangs on trying to complete Building vscodium:

`` ==> Tidying install...
-> Removing libtool files... -> Purging unwanted files... -> Removing static library files... -> Compressing man and info pages... ==> Checking for packaging issues... ==> WARNING: Package contains reference to $srcdir usr/share/vscodium/resources/app/extensions/microsoft-authentication/dist/extension.js ==> Creating package "vscodium"... -> Generating .PKGINFO file... -> Generating .BUILDINFO file... -> Generating .MTREE file... -> Compressing package... ==> Leaving fakeroot environment. ==> Finished making: vscodium 1.96.4.25017-1 (Tue 21 Jan 2025 09:50:19 PM) ==> Cleaning up...

``

kajika91 commented on 2024-11-29 08:34 (UTC)

The interaction with menu bar seems to be fixed as of version 1.95.3 (I also checked the PR https://github.com/NixOS/nixpkgs/pull/358857).

I had the same issue with version 1.95.2 and upgrading to 1.95.3 fixed it.

1 2 3 4 5 6 .. 12 Next › Last »