Arch Linux User Repository

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

@Ranguna

Have you tried installing this package first? Looks like some other package is writing to electron's paths

Can you please add debugedit to build dependencies of this pacakge? Otherwise, it prints errors about command not being found when building package (the build succeds anyway though).

I'm getting the following error when installing, I have electron27-bin as a dependency of another package I use:

vscodium-bin-debug: /usr/lib/debug/.build-id/21/d4e07fcf10f30bb538db018c3691202f7496ca exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/21/d4e07fcf10f30bb538db018c3691202f7496ca.debug exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/31/67ad6b32c635dff5a94dad8a8d2d4da669974d exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/31/67ad6b32c635dff5a94dad8a8d2d4da669974d.debug exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/a9/049dae268525b4a336acaefd7bf30dc6fa31e6 exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/a9/049dae268525b4a336acaefd7bf30dc6fa31e6.debug exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/b3/ae6bf4d0e66496320a9e91f34c0137908b4699 exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/b3/ae6bf4d0e66496320a9e91f34c0137908b4699.debug exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/d6/dbb4c112131521d32d30fcbb6e290f8bbfd58c exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/d6/dbb4c112131521d32d30fcbb6e290f8bbfd58c.debug exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/e7/d5fe2cd951b5c7111544c56de2b95a6c82070d exists in filesystem (owned by electron27-bin-debug)
vscodium-bin-debug: /usr/lib/debug/.build-id/e7/d5fe2cd951b5c7111544c56de2b95a6c82070d.debug exists in filesystem (owned by electron27-bin-debug)

I'm also getting the errors above when attempting to install alongside the vscodium insider bin package.

@OliverP Right, looks like the setuid bit isn't set for chrome-sandbox.

I tried to put chmod u+s "/opt/${pkgname}/chrome-sandbox" in the package() function without luck. Seems like fakeroot is inhibiting that.

If you'd like this fixed, please find an example of how to set the setuid bit in PKGBUILD :)

The linux-hardened kernel is having problems with the permissions on the sandbox binary.

When running vscodium --verbose I get the following:

[10348:0219/095332.323866:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/vscodium-bin/chrome-sandbox is owned by root and has mode 4755.

@pizero I'm hesitant adding this to the .desktop file. You can add the flag to the file ~/.config/codium-flags.conf. Then, it'll be ran with that flag IIRC. This is displayed when installing the package :)

@ArchUsr1 Wayland support is patchy. Those warnings are expected. For me (Hyprland), Wayland doesn't work at all. Consider using the non-wayland application shortcut instead. This is an upstream issue.

是否可以将 --enable-wayland-ime 添加到 vscodium-bin-wayland.desktop 以支持 Wayland 中的输入法，例如 fcitx5 等。

(bing) Is it possible to add --enable-wayland-ime to vscodium-bin-wayland.desktop to support input methods in Wayland such as fcitx5 etc.

...
5 -- Exec=/usr/bin/codium --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland --unity-launch %F
5 ++ Exec=/usr/bin/codium --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland --enable-wayland-ime --unity-launch %F
...
17 -- Exec=/usr/bin/codium --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland --new-window %F
17 ++ Exec=/usr/bin/codium --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland --enable-wayland-ime --new-window %F
...

I'm experiencing graphical glitches when running Wayland and window fails to render properly. I'm on KDE Plasma with Wayland session. I see some warnings in journalctl (reverse order):

Feb 06 14:11:39 MK4A kwin_wayland[1290]: kwin_core: Cannot grant a token to KWaylandServer::ClientConnection(0x5e617cea76a0)
Feb 06 14:11:39 MK4A plasmashell[6434]: Warning: 'ozone-platform' is not in the list of known options, but still passed to Electron/Chromium.
Feb 06 14:11:39 MK4A plasmashell[6434]: Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Feb 06 14:11:39 MK4A systemd[1243]: Started VSCodium - Text Editor.

@BachoSeven Sorry for the late answer, and thanks for pointing it out. The latest patch parses the codium-flags.conf to allow both methods: you can have one option per line or several per line. Its simply white-space separated now.

Please let me know if you have any further issues.