Change:
command: electron-launch $SNAP/usr/share/@@NAME@@/bin/@@NAME@@ --no-sandbox common-id: @@NAME@@.desktop environment: <del> DISABLE_WAYLAND: 1 </del> GSETTINGS_SCHEMA_DIR: $SNAP/usr/share/glib-2.0/schemas url-handler: command: electron-launch $SNAP/usr/share/@@NAME@@/bin/@@NAME@@ --open-url --no-sandbox environment: <del> DISABLE_WAYLAND: 1 </del> GSETTINGS_SCHEMA_DIR: $SNAP/usr/share/glib-2.0/schemas

Discussion:
Issue Type: <bBug</bTrying to start code using Ozone Wayland crash with the following log Electron 17.3.1 was supposed to fix Wayland crashes, so I guess this is a new one :-( VS Code version: Code - Insiders 1.67.0-insider (, 2022-04-06T05:16:11.110Z) OS version: Linux x64 5.16.14-1-MANJARO snap Electron: 17.3.1 Chromium: 98.0.4758.141 16.13.0 V8: 9.8.177.13-electron.0 Restricted Mode: No Compositor and DE: plasmashell 5.24.3 kwin 5.24.3 <details<summarySystem Info</summary </details
Crash due to the following error . What is the output of and ?
is unset and . edit sorry for the extra ping, I was not sure you had been notified :-)
More information using
do you need any other info?
Update: this does not happen in native vscodium with the following version So maybe it's an issue with the snap packaging?
I am using Fedora 36, VSCode 1.67.1 from microsoft repositories. now works mostly, however, the window disappears immediately after resizing. The processes remain in the background, but the window is gone. Maximizing and minimizing the window however do not cause the issue. Edit: see
Do you need more info on this?
I just noticed is Wayland intentionally disabled for snaps?
removing it was all that was needed for Chromium. I'm opening a PR to try that.
sorry for the delayed response, I missed the notifications around this issue. Just saw the PR you had created, thanks for working on it. Regarding why the variable was , it was from which was when the runtime did not support wayland backend. Since it is no longer the case, I agree with removing the flag.
Hi No worries and thank you very much for having a look!
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected.

If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
Unfortunately the bug still seems to be present, with no change in the error message so now I'm wondering if might be the issue (or the solution I guess).
Reopening because of what mentioned.
Edit: It works on my system now. Both Insiders and default version works fine. Since they both started working at the same time I would conclude my issue had to be on my system. I don't know what might have fixed it yet. It does not work neither on insiders nor on stable as of now. Here are mine logs similar to OP.
Unable to repro the issue with latest insiders, can you confirm.
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
Yes, I can repro with 1.75.0-insider ()
Clean installation of Kubuntu 22.10 this morning: installing vscode via snap/discover results in this crash. Installing the deb from runs successfully under Wayland.
Happy to report that fixed it indeed, thanks a lot !
Thanks for confirming :)