VSCode Snap doesn't start when using Wayland mode

[major-mayer]

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

• VS Code Version: 1.86.0-insider fb769554405bee9be16e21ceb0a496bd29126941 x64

• OS Version: Ubuntu 23.10

Steps to Reproduce:

1. Download the code-insiders snap package
2. Run it like this: code-insiders --ozone-platform-hint=auto --verbose
3. VSCode doesn't start but reports this in the console:

 Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.
MESA-LOADER: failed to open radeonsi: /usr/lib/dri/radeonsi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
failed to load driver: radeonsi
MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
failed to load swrast driver
[340245:0109/202358.589994:WARNING:wayland_object.cc(158)] Binding to gtk_shell1 version 4 but version 5 is available.
[340245:0109/202358.590067:WARNING:wayland_object.cc(158)] Binding to zwp_pointer_gestures_v1 version 1 but version 3 is available.
[340245:0109/202358.590093:WARNING:wayland_object.cc(158)] Binding to zwp_linux_dmabuf_v1 version 3 but version 4 is available.
(code-insiders:340245): GLib-GIO-ERROR **: 20:23:58.596: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

[brianfcoleman]

I believe that this issue is caused by a bug in the VSCode snapcraft.yaml.

• The VSCode snap is using confinement: classic and base: core20. As such it is based on Ubuntu 20.04
• According to this discussion on the Snapcraft forum, with the current VSCode snapcraft.yaml, mesa will attempt to load the host dri drivers. This will work by chance on Ubuntu 20.04, but will fail on Ubuntu 22.04.
• This can be fixed by installing the libgl1-mesa-dripackage into the snap and configuring LIBGL_DRIVERS_PATH to point to the dri driver directory within the snap.
• I have not tested the following patch but I believe that something like this would potentially fix this issue. The patch is based on the egmde-snap sample and the test-gl sample mentioned in the Snapcraft forum discusstion

--- snapcraft.yaml  2024-04-01 18:39:12.742475423 +0100
+++ snapcraft-mesa.yaml 2024-04-01 18:45:08.677398621 +0100
@@ -70,12 +70,30 @@
         cd "/snap/$snap/current" && find . -type f,l -exec rm -f "$SNAPCRAFT_PRIME/{}" \;
       done
       patchelf --print-rpath $SNAPCRAFT_PRIME/usr/share/@@NAME@@/chrome_crashpad_handler
+  mesa-patchelf:
+    plugin: nil
+    stage-packages:
+    - libgl1-mesa-dri
+    stage:
+      # The libraries in .../dri need no-patchelf, so they come from the mesa-unpatched part
+      - -usr/lib/${SNAPCRAFT_ARCH_TRIPLET}/dri
+  mesa-no-patchelf:
+    plugin: nil
+    stage-packages:
+      - libgl1-mesa-dri
+    build-attributes:
+      - no-patchelf # Otherwise snapcraft may strip the build ID and cause the driver to crash
+    stage:
+      # Only the libraries in .../dri need to not be patched, the rest come from the mesa part
+      - usr/lib/${SNAPCRAFT_ARCH_TRIPLET}/dri

 apps:
   @@NAME@@:
     command: electron-launch $SNAP/usr/share/@@NAME@@/bin/@@NAME@@ --no-sandbox
     common-id: @@NAME@@.desktop
+    environment:
+      LIBGL_DRIVERS_PATH: $SNAP/usr/lib/${SNAPCRAFT_ARCH_TRIPLET}/dri

   url-handler:
     command: electron-launch $SNAP/usr/share/@@NAME@@/bin/@@NAME@@ --open-url --no-sandbox

[deepak1556]

Thanks @brianfcoleman , the mesa driver issue would be good solve but that is not the direct cause of this issue. We would need to address the incorrect settings configured for snap (code-insiders:340245): GLib-GIO-ERROR **: 20:23:58.596: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

[FredHaa]

Any updates on this issue?

[MadeManMax]

Any updates on this issue?

I've removed snap version and installed deb from https://code.visualstudio.com/docs/setup/linux and this fixed it for me.

[galpar]

Any updates on this? Having the ELECTRON_OZONE_PLATFORM_HINT set to auto crashes the application, and I woudn't want to remove that, so other electron apps can read it and scale properly.