VS Code 1.107.0 shows black screen on Debian unless launched with --disable-gpu

[E-Rinaudo]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.107.0
• OS Version: Debian 13

Steps to Reproduce:

1. Launch VS Code normally (just code from terminal or app icon).
2. The window opens but shows a completely black screen, nothing else.
3. Launching with 'code --disable-gpu' fixes the issue.

[deepak1556]

Can you share the logs from running code --verbose

[E-Rinaudo]

Here are the relevant logs from 'code --verbose' that show the issue:

[20361:1211/155107.208233:WARNING:ui/ozone/platform/wayland/common/drm_render_node_path_finder.cc:111] Preferred drm_render_node not found, picking nouveau
[20361:1211/155107.683571:WARNING:ui/ozone/platform/wayland/common/wayland_object.cc:119] Binding to wl_seat version 8 but version 9 is available.
[20361:1211/155107.683616:WARNING:ui/ozone/platform/wayland/common/wayland_object.cc:119] Binding to zwp_pointer_gestures_v1 version 1 but version 3 is available.
[20361:1211/155107.683688:WARNING:ui/ozone/platform/wayland/common/wayland_object.cc:119] Binding to org_kde_kwin_appmenu_manager version 1 but version 2 is available.
Gtk-Message: 15:51:07.970: Failed to load module "appmenu-gtk-module": 'gtk_module_display_init': /usr/lib/x86_64-linux-gnu/gtk-3.0/modules/libwindow-decorations-gtk-module.so: undefined symbol: gtk_module_display_init
[20361:1211/155108.412609:WARNING:ui/ozone/platform/wayland/host/wayland_surface.cc:170] Server doesn't support zcr_alpha_compositing_v1.
[20361:1211/155108.412638:WARNING:ui/ozone/platform/wayland/host/wayland_surface.cc:185] Server doesn't support overlay_prioritizer.

[deepak1556]

What is the output of ls /dev/dri ?

Can you try overriding the drm node with --render-node-override flag and see if it works without disabling gpu ?

[E-Rinaudo]

ls /dev/dri output:
by-path card0 renderD128

I also tried launching with --render-node-override. It gave a warning:
Warning: 'render-node-override' is not in the list of known options, but still passed to Electron/Chromium.

VS Code now works without --disable-gpu.

[deepak1556]

Yeah the warning can be ignored, good to know. Then it looks like an issue in the drm node detection code in upstream https://source.chromium.org/chromium/chromium/src/+/main:ui/ozone/platform/wayland/common/drm_render_node_path_finder.cc

[E-Rinaudo]

Great to know. Thanks for looking into this.