Package Details: vscodium-bin 1.90.2.24171-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: 285
Popularity: 11.99
First Submitted: 2020-09-23 18:58 (UTC)
Last Updated: 2024-06-19 19:01 (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 .. 22 Next › Last »

BachoSeven commented on 2023-08-05 18:19 (UTC) (edited on 2023-08-05 18:23 (UTC) by BachoSeven)

@Icelk I can't help but notice some inconsistency in the handling of the *-flags.conf scripts for Chromium/Electron-based applications across Arch packages:

Since chromium is the basis of Electron applications, I think that having the flags one per line could be the default; in my opinion, it also improves the readability of the configuration file.

I hope this is useful, let me know if I got something wrong.

mboquien commented on 2023-07-23 13:58 (UTC)

When running under a Wayland GNOME session, the decorations are not displayed. Modifying the .desktop file to add the --enable-features=WaylandWindowDecorations option fixes the issue.

OdnetninI commented on 2023-07-12 08:22 (UTC)

Hey guys. Something weird is happening with vscodium-bin 1.80.0.23188. I am using the wayland version ( --enable-features=UseOzonePlatform --ozone-platform=wayland --no-sandbox --unity-launch ). However, it does not connect to ssh using the Open-VSX -> Open Remote - SSH plugin. I tried different things, but for now I am sticking to vscodium-bin-1.79.2.23166.

Do you have the same problem?

sandroid commented on 2023-07-10 20:27 (UTC)

Hey, I was wondering why --no-sandbox is used in the .desktop files. Upstream seems to have changed that a while ago, see https://github.com/microsoft/vscode/pull/122909

Icelk commented on 2023-07-09 11:53 (UTC)

@griffi-gh That is by design. You can select which apps you wish to be the defaults.

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.