Package Details: vscodium-bin 1.99.02289-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: 326
Popularity: 8.33
First Submitted: 2020-09-23 18:58 (UTC)
Last Updated: 2025-04-05 11:00 (UTC)

Pinned Comments

sperg512 commented on 2021-05-12 00:31 (UTC) (edited on 2024-06-04 15:14 (UTC) by sperg512)

@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 2 3 4 5 6 7 8 9 10 11 12 .. 25 Next › Last »

krims0n commented on 2023-07-05 09:02 (UTC) (edited on 2023-07-05 11:45 (UTC) by krims0n)

I am getting random crashes when enabling wayland on startup. 9 out of 10 times it briefly shows the GUI, then crashes.

I get this error:

ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

This happens on the ms version as well. Without wayland it works, but obviously not what I want. Any ideas?

Edit: I downgraded to vscodium-bin-1.79.1.23164-1, seems to work now.

Edit2: nope, worked fine for a while, restarted and crashes again. Also with 1.78 and extensions disabled.

Edit3: workaround: https://github.com/microsoft/vscode/issues/181533#issuecomment-1597187136

griffi-gh commented on 2023-07-02 22:48 (UTC)

Creates a bunch of unneeded file associations by default. (all folders and image files open in VSCodium)

begin-theadventu commented on 2023-06-16 09:37 (UTC)

sudo ln -fs /opt/vscodium-bin/codium /usr/bin/vscodium; sudo rm /usr/share/applications/codium-wayland.desktop

jronald commented on 2023-06-15 11:47 (UTC)

a note when install

==> NOTE: Custom flags should be put directly in: ~/.config/codium-flags.conf

Icelk commented on 2023-06-15 07:46 (UTC)

@michaelskyf I'll revert that immediately! Thanks for reporting it.

Icelk commented on 2023-06-15 07:46 (UTC)

@jronald AUR packages can't be built on file system which do not support symbolic links (e.g. samba). Your issue should affect every package, not just this. Glad you resolved it!

jronald commented on 2023-06-14 17:35 (UTC) (edited on 2023-06-15 06:59 (UTC) by jronald)

EDIT works well for a normal path instead of samba

$ makepkg
...
==> Extracting sources...
ln: failed to create symbolic link '/home/abc/nuc_share/archlinux/aur/vscodium-bin/src/vscodium-bin.desktop': Operation not supported
ln: failed to create symbolic link '/home/abc/nuc_share/archlinux/aur/vscodium-bin/src/vscodium-bin-uri-handler.desktop': Operation not supported
ln: failed to create symbolic link '/home/abc/nuc_share/archlinux/aur/vscodium-bin/src/vscodium-bin.install': Operation not supported
ln: failed to create symbolic link '/home/abc/nuc_share/archlinux/aur/vscodium-bin/src/vscodium-bin.sh': Operation not supported
ln: failed to create symbolic link '/home/abc/nuc_share/archlinux/aur/vscodium-bin/src/vscodium-bin-wayland.desktop': Operation not supported
ln: failed to create symbolic link '/home/abc/nuc_share/archlinux/aur/vscodium-bin/src/VSCodium-linux-x64-1.79.1.23164.tar.gz': Operation not supported

samba mounted on /home/abc/nuc_share

michaelskyf commented on 2023-06-14 07:59 (UTC) (edited on 2023-06-14 09:13 (UTC) by michaelskyf)

Hi! For some reason Codium wasn't launching for me under pure wayland session after an update. I had flags set in codium-flags.conf, but it looked like the program wasn't reading them. The solution was to remove "" around $CODE_USER_FLAGS from vscodium-bin.sh

...
# Launch
exec /opt/vscodium-bin/bin/codium "$@" "$CODE_USER_FLAGS"

...
# Launch
exec /opt/vscodium-bin/bin/codium "$@" $CODE_USER_FLAGS

The commit that introduced the bug: f89ac63d1886

Icelk commented on 2023-06-12 20:53 (UTC)

@manuth Thanks! The problem with changing the WMClass is that under xorg (and xwayland), it still has the VSCodium class. I'll create another .desktop entry with wayland options.

manuth commented on 2023-06-09 10:57 (UTC)

For whatever reason, when launching VSCodium with --ozone-platform-hint=wayland, the window class is codium-url-handler. I think it might make sense to reflect this in the StartupWMClass of codium.desktop.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 25 Next › Last »