Closed AdelKS closed 1 year ago
Facing the same issue on Arch Linux (GNOME 43.5)
UPDATE: Just tested the insider version, it seems to be working on insiders. This issue probably has something to do with electron
Most likely Wayland's update 1.22 does this.
I'm also running Arch Linux with KDE and Wayland.
I have first noticed this behavior on Firefox with ENV var MOZ_ENABLE_WAYLAND=1 https://bugzilla.mozilla.org/show_bug.cgi?id=1826583
Same happens with VSCode obviously....
I changed the Optimus mode from Hybrid
to Integrated
mode using supergfxctl
, and vscode
now works under wayland on Gnome, maybe an update fixed this and has nothing to do with Optimus, will update this answer.
Edit: I confirm that it's Optimus related. When moving to integrated
graphics only, vscode
works in wayland mode in both KDE and GNOME. When switching between hybrid
and integrated
firefox stops working too, and I need to reset its settings so it can start. Not sure what's happening.
Closing per above comment given issue is not from VSCode.
Does this issue occur when all extensions are disabled?: Yes
Running
vscode --verbose
with.config/code-flags.conf
filled with--ozone-platform-hint=auto
gives this outputI will attach some more information after reading #146890
$GDK_BACKEND
is unset$WAYLAND_DISPLAY
is set towayland-0
WAYLAND_DEBUG=1 code --verbose
: vscode-wayland-debug.txtThank you for your work and help