| 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: | 327 |
| Popularity: | 8.61 |
| First Submitted: | 2020-09-23 18:58 (UTC) |
| Last Updated: | 2025-04-09 18:00 (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.
KDE launcher stopped working. Now I have to manually type vscodium on a terminal for it to open. The wayland change broke the package for me.
@mistersmee it should be fixed now
install: cannot stat '/tmp/makepkg/vscodium-bin/src/vscodium-bin-wayland.desktop': No such file or directory
==> ERROR: A failure occurred in package().
You need to remove references to vscodium-bin-wayland.desktop in package() as well.
I think you could remove vscodium-bin-wayland.desktop if you use --ozone-platform-hint=auto instead of --ozone-platform=wayland in vscodium-bin.desktop.
According to Electron docs (https://www.electronjs.org/docs/latest/api/environment-variables):
ELECTRON_OZONE_PLATFORM_HINT Linux
Selects the preferred platform backend used on Linux. The default one is x11. auto selects Wayland if possible, X11 otherwise.
Options:
auto
wayland
x11
Tested and launches in Wayland for me
You still need --enable-features=UseOzonePlatform,WaylandWindowDecorations
@xorly
Nope. I just checked and when I launch I get xwayland:
Window 5a9f94e6ce90 -> Release Notes: 1.99.02289 - VSCodium:
mapped: 1
hidden: 0
at: 10,1300
size: 1264,690
workspace: 1 (1)
floating: 0
pseudo: 0
monitor: 1
class: VSCodium
title: Release Notes: 1.99.02289 - VSCodium
initialClass: VSCodium
initialTitle: VSCodium
pid: 105233
xwayland: 1
Are you sure you don't have any flags in ~/.config/codium-flags.conf?
I think the vscodium-bin-wayland.desktop is not needed anymore.
vscodium-bin.desktop launches fine, no scaling issues etc. Sway does not detect it as xwayland app (though, killing xwayland terminates vscode no matter which desktop entry is used).
Nevermind, it just appeared like that in the writing box...
@drakkar1969 It should be fixed now! (why is it censoring fix? as in f i x)
With the latest version, in Wayland the WMClass is codium, while the StartupWMClass is codium-url-handler in the desktop launcher vscodium-bin-wayland
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.