Package Details: vscodium-bin 1.88.1.24104-1

Git Clone URL: https://aur.archlinux.org/vscodium-bin.git (read-only, click to copy)
Package Base: vscodium-bin
Description: Binary releases of VS Code without MS branding/telemetry/licensing.
Upstream URL: https://github.com/VSCodium/vscodium
Licenses: MIT
Conflicts: vscodium
Provides: codium, vscode, vscodium
Submitter: ckatri
Maintainer: sperg512 (Icelk)
Last Packager: Icelk
Votes: 271
Popularity: 7.69
First Submitted: 2020-09-23 18:58 (UTC)
Last Updated: 2024-04-13 02:01 (UTC)

Pinned Comments

sperg512 commented on 2021-05-12 00:31 (UTC)

hey guys, @Icelk set up a script that checks for new releases and pushes updates if there are any new ones. I believe it runs every hour so there's no need to flag OOD, unless there's something that needs changed with the PKGBUILD

Latest Comments

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 22 Next › Last »

Icelk commented on 2021-12-17 10:14 (UTC)

@KDN_Observer

It seems like no other distribution of VSCode does this. Could you provide the diff of the PKGBUILD to change this?

KDN_Observer commented on 2021-12-10 07:27 (UTC)

As per Electron package guidelines, packages that contain a prebuilt copy of electron shall be installed in /opt/appname rather in /usr/share. Please change your PKGBUILD to either 1) remove the bundled electron and use the system one instead or 2) install inside the /opt/vscodium-bin directory

Icelk commented on 2021-11-27 12:37 (UTC)

@animo Are the checksums good now?

Icelk commented on 2021-11-27 12:37 (UTC)

@indicozy Try reinstalling electron. Don't think any electron app should throw a Segmentation fault, ever.

livem commented on 2021-11-26 21:27 (UTC)

@indicozy, Which version you meant update to?

In order to try to reproduce, I re-installed the package. I got the same version as was a week ago already. I see no any issue for me after that reinstallation.


~/Desktop ❯ vscodium
~/Desktop ❯

vscodium about window:


Version: 1.62.3
Commit: ccbaa2d27e38e5afa3e5c21c1c7bef4657064247
Date: 2021-11-19T00:20:00.672Z
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.15.5-1-MANJARO

Probably some dependency issue. Try to go fix them (you see them in above). May be to refresh kernel is also a possible solution.

Also I am a bit "alien" to Arch Linux (so possibly have a bit different environment):


Operating System: Manjaro Linux
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.15.5-1-MANJARO (64-bit)
Graphics Platform: X11

indicozy commented on 2021-11-26 20:47 (UTC) (edited on 2021-11-26 20:47 (UTC) by indicozy)

after update I got a bug:

$ vscodium
/usr/bin/vscodium: line 53: 38749 Segmentation fault      ELECTRON_RUN_AS_NODE=1 "$ELECTRON" "$CLI" --ms-enable-electron-run-as-node "$@"

Did anyone get the same issue?

animo commented on 2021-11-15 20:39 (UTC)

The 1.62.2 sha256 sum for the ARM64 architecture is wrong in PKGBUILD, here's the correct one: 3a7b9931ab1bc3432ba6e4323c7f0caf280e236d95fc6b30c6cb24e9af925f02 .

Icelk commented on 2021-11-07 12:25 (UTC)

Hi @3y3p4tch! I believe it is to allow all features like reading workspaces and other content in the .vscode directory.

Check the vscode docs (or something), since it's just an argument to vscode.

3y3p4tch commented on 2021-11-06 05:32 (UTC)

Hi maintainers, I noticed that vscodium-bin.desktop contains 'no-sandbox'. Any particular reason for it being there? If not, then could it be removed? (My build works perfectly without no-sandbox)

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 22 Next › Last »