Package Details: vscodium-bin 1.99.32562-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: 328
Popularity: 7.77
First Submitted: 2020-09-23 18:58 (UTC)
Last Updated: 2025-04-16 19: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

1 2 3 4 5 6 .. 26 Next › Last »

nfp0 commented on 2025-04-18 14:40 (UTC)

@Icelk @bermudi It was working just fine for me on KDE Wayland. What error were you getting?

The only strange thing is that it opens minimized. But the same happens when I use the current "VSCodium - Wayland" one.

bermudi commented on 2025-04-14 18:32 (UTC)

@Icelk much appreciated

Icelk commented on 2025-04-13 08:29 (UTC)

@bermudi I reverted the changes in the latest release. @joern_h great, thanks! It's added.

joern_h commented on 2025-04-10 08:08 (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.

bermudi commented on 2025-04-10 03:22 (UTC) (edited on 2025-04-10 03:23 (UTC) by bermudi)

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.

Icelk commented on 2025-04-08 13:45 (UTC)

@mistersmee it should be fixed now

mistersmee commented on 2025-04-08 13:41 (UTC) 

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.

drakkar1969 commented on 2025-04-06 17:41 (UTC) (edited on 2025-04-06 17:44 (UTC) by drakkar1969)

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

Icelk commented on 2025-04-05 12:27 (UTC)

@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?

xorly commented on 2025-03-28 12:03 (UTC)

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).

1 2 3 4 5 6 .. 26 Next › Last »