| 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: | 306 |
| Popularity: | 11.17 |
| First Submitted: | 2020-09-23 18:58 (UTC) |
| Last Updated: | 2024-09-12 19:00 (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?
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
@griffi-gh That is by design. You can select which apps you wish to be the defaults.
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
Creates a bunch of unneeded file associations by default. (all folders and image files open in VSCodium)
sudo ln -fs /opt/vscodium-bin/codium /usr/bin/vscodium; sudo rm /usr/share/applications/codium-wayland.desktop
a note when install
==> NOTE: Custom flags should be put directly in: ~/.config/codium-flags.conf
@michaelskyf I'll revert that immediately! Thanks for reporting it.
@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!
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
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.