vscodium: Can't run in wayland

Describe the bug Can’t run in wayland with this flags codium --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland ms-vscode on the other hand does work normally

Please confirm that this problem is VSCodium-specific

This bug doesn’t happen if I use Microsoft’s Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn’t already documented

I checked the Docs page and my issue is not mentioned there.

To Reproduce Steps to reproduce the behavior:

install as snap
try to open as wayland

codium --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland

Expected behavior vscode wayland window

Screenshot

Desktop (please complete the following information):

OS: Ubuntu 23.04
Architecture: x86_64
Version: 1.82.2
App Manager: Snap
Sandboxed: Snap (classic mode)

Additional context Both vscode and vscodium print two warning messages but vscodium refuses to pop up.

About this issue

Original URL
State: open
Created 9 months ago
Reactions: 15
Comments: 24 (1 by maintainers)

Most upvoted comments

similar issue here when vscodium is run in native wayland, it just immediately closes

negativeExponent on Sep 23, 2023

Have you tried with the setting (VSCodium’s settings.json) "window.titleBarStyle": "custom"? (from https://github.com/microsoft/vscode/issues/184124)

daiyam on Sep 26, 2023

Same issue here. Suddenly vscodium not working any longer.

Tried re-installing after a purge with apt, tried previous version, all to no avail.

Running debian KDE under wayland on x64.

Any way around this? Or do I need install another IDE?

I found the answer: running from the console with the follwing as suggested by Master811129] above works for me. “codium --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland”

I also changed the menu accordingly and that works as well!

Thanks @Master811129

MidGe48 on Oct 4, 2023

It looks like the Issue has been fixed for me in 1.87.0.

Version: 1.87.0
Release: 24060
Commit: 5695cc889d3d0500fa6c7983468a699185fce828
Date: 2024-02-29T23:06:19.600Z
Electron: 27.3.2
ElectronBuildId: undefined
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Linux x64 6.5.0-21-generic snap

Master811129 on Mar 1, 2024

upstream VSCode doesn’t have this issue so what is it doing differently? apart from telemerty 😂

regulator-g on Jan 16, 2024

Using custom title bar style solved the problem for me. I also use the --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland start options.

xotakfr on Oct 23, 2023

@daiyam Yes I tried it in both native and custom. It didn’t change anything. same issue

Master811129 on Sep 27, 2023

A similar issue here in arch with flatpak version, however vscodium on arch repo work great

but my warning is:

Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.

Desktop

OS: Arch Linux
Architecture: x86_64
Version: 1.82.0.23250
App Manager: flatpak
Sandboxed: flatpak

ls1w on Sep 20, 2023

@loulou310 Thank you, it worked for me! However I had a little issue, could you explain for dummies how to make those flags persist? It’s not ideal to type them every time I want to lunch vscodium.

You can edit the .desktop file. They are located in /usr/share/applications. Then in the file, in front of Exec, you can see the command that is executed to launch the app. You can add the flags before the %F. Also, lower in the file there’s another Exec that is for new windows, I believe you need to change it here too.

xotakfr on Dec 31, 2023

Been having this issue for a while now, first on Arch, then on NixOS

DrymarchonShaun on Sep 24, 2023