Can't run in wayland

[Ma5t3rful]

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

• [x] 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

• [x] I checked the Docs page and my issue is not mentioned there.

To Reproduce Steps to reproduce the behavior:

1. install as snap
2. 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.

[ls1w]

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

[mcendu]

Same issue; cannot reliably reproduce the issue after attempting to run with gdb.

• OS: Gentoo with Linux 6.5.4
• Architecture: amd64
• Version: 1.82.2.23257
• App Manager: Portage
• Sandboxed: no

[rxmmah]

i have the same issue the app quite after 2 seconds

[negativeExponent]

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

[RalfJung]

EDIT: Sorry, I only now realize I posted this in the vscodium bugtracker, not the one for the flatpak.

[DrymarchonShaun]

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

[rxmmah]

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

and there are no solutions for it online, this is strange.

[daiyam]

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

[DrymarchonShaun]

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

Yeah, I'm not sure if it helped. The issue is inconsistent either way, so it's hard to tell if it did anything.

[Ma5t3rful]

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

[MidGe48]

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

[ls1w]

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

You can run as xwayland instead wayland, this work for me at list, you can run on x11 session too

[DrymarchonShaun]

You can run as xwayland instead wayland

So far this is the only thing that has solved this for me.

[xotakfr]

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

[madhums]

Any update on this? Is there one setting somewhere to make this work regardless of whether you open the app from terminal or GUI? Anyone willing to share a solution and perhaps update the documentation?

[dR3b]

Arch linux and Sway, Xwayland is working but with:

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

The Codium window closes immediately and the process is ended.

[TenEXP]

Arch linux and Sway, Xwayland is working but with:

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

The Codium window closes immediately and the process is ended.

For me, it doesn't close immediately, but as soon as I move a mouse cursor over any part of its window.

[omnigenous]

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

[xotakfr]

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

[regulator-g]

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

[Hellscaped]

I actually had this issue earlier and fixed it, but another one arose: the window was tiny inside my window, when i moved my mouse to the bottom left of the full window it showed that it was registering mouse events at the real pos but rendering as a tiny window

[JFincher42]

Same issue here on EndeavourOS (Arch)

VSCodium installed from AUR, no combination of CLI options works to force Wayland

Version: 1.85.2 Release: 24019 Commit: c8a36a69377856369f139f39ee56dd3838130fbf Date: 2024-02-03T22:34:16.729Z Electron: 25.9.7 ElectronBuildId: undefined Chromium: 114.0.5735.289 Node.js: 18.15.0 V8: 11.4.183.29-electron.0 OS: Linux x64 6.7.4-arch1-1

[Ma5t3rful]

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

[negativeExponent]

its appears that wayland mode is indeed working. built from Arch-AUR