| 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: | 326 |
| Popularity: | 8.33 |
| First Submitted: | 2020-09-23 18:58 (UTC) |
| Last Updated: | 2025-04-05 11:00 (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?
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
@PEAR, @hawkeye116477 Same issue here. Update on this issue can be followed here: https://github.com/VSCodium/vscodium/issues/2082
From the issue thread, someone has a fix:
Open your VSCodium settings with Ctrl + , and search "title bar style" and set the value of "Window: Title Bar Style" from "native" to "custom". Restart VSCodium.
@PEAR I can confirm, I had same problem with code package from Extra repo.
Starting from the current version, vscodium-bin-wayland.desktop seems to open an X11 window for me rather than the intended Wayland one. Using Plasma as DE. Is anyone else getting the same issue?
Though ime works by adding "~/.config/codium-flags.conf" with "--enable-wayland-ime", there is a warning as below when launching vscodium from console.
$ codium
Warning: 'enable-wayland-ime' is not in the list of known options, but still passed to Electron/Chromium.
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.