vscode: Unable to launch on latest wl_roots due to Chromium bug

On Fedora 34 the stable VSCode version launches fine with the Wayland flags but the latest insider version on Electron 17 is still broken.

/usr/share/code-insiders/code-insiders --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland --verbose
[34361:0311/101739.989925:ERROR:gpu_init.cc(454)] Passthrough is not supported, GL is egl, ANGLE is 
[34361:0311/101739.994136:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'ozone-platform' is not in the list of known options, but still passed to Electron/Chromium.
[main 2022-03-11T09:17:40.064Z] [File Watcher (node.js)] Request to start watching: /home/tim/.config/Code - Insiders/User (excludes: <none>),/home/tim/.config/Code - Insiders/User/settings.json (excludes: <none>)
[main 2022-03-11T09:17:40.085Z] Starting VS Code
[main 2022-03-11T09:17:40.085Z] from: /usr/share/code-insiders/resources/app
[main 2022-03-11T09:17:40.085Z] args: {
  _: [],
  diff: false,
  add: false,
  goto: false,
  'new-window': false,
  'reuse-window': false,
  wait: false,
  help: false,
  'list-extensions': false,
  'show-versions': false,
  'pre-release': false,
  version: false,
  verbose: true,
  status: false,
  'prof-startup': false,
  'no-cached-data': false,
  'prof-v8-extensions': false,
  'disable-extensions': false,
  'disable-gpu': false,
  'ms-enable-electron-run-as-node': false,
  telemetry: false,
  debugRenderer: false,
  logExtensionHostCommunication: false,
  'skip-release-notes': false,
  'skip-welcome': false,
  'disable-telemetry': false,
  'disable-updates': false,
  'disable-keytar': false,
  'disable-workspace-trust': false,
  'disable-crash-reporter': false,
  'crash-reporter-id': '3511cf87-8c3e-4b95-ab73-d683ffaa7383',
  'skip-add-to-recently-opened': false,
  'unity-launch': false,
  'open-url': false,
  'file-write': false,
  'file-chmod': false,
  'driver-verbose': false,
  force: false,
  'do-not-sync': false,
  trace: false,
  'force-user-env': false,
  'force-disable-user-env': false,
  'open-devtools': false,
  __sandbox: false,
  'no-proxy-server': false,
  'no-sandbox': false,
  nolazy: false,
  'force-renderer-accessibility': false,
  'ignore-certificate-errors': false,
  'allow-insecure-localhost': false,
  'disable-dev-shm-usage': false,
  logsPath: '/home/tim/.config/Code - Insiders/logs/20220311T101740'
}
[main 2022-03-11T09:17:40.088Z] Resolving machine identifier...
[main 2022-03-11T09:17:40.089Z] Resolved machine identifier: 6d2546bf2b07ccd4257f1f46389f17d48e952d03ad7dab8e50a0ec4476d20c56
[main 2022-03-11T09:17:40.090Z] Main->SharedProcess#connect
[main 2022-03-11T09:17:40.095Z] [File Watcher (node.js)] Started watching: '/home/tim/.config/Code - Insiders/User'
[main 2022-03-11T09:17:40.096Z] [File Watcher (node.js)] Error: ENOENT: no such file or directory, stat '/home/tim/.config/Code - Insiders/User/settings.json'
[main 2022-03-11T09:17:40.101Z] StorageMainService: creating global storage
[main 2022-03-11T09:17:40.110Z] lifecycle (main): phase changed (value: 2)
[main 2022-03-11T09:17:40.111Z] windowsManager#open
[main 2022-03-11T09:17:40.111Z] windowsManager#open pathsToOpen [
  {
    backupPath: '/home/tim/.config/Code - Insiders/Backups/1646989352923',
    remoteAuthority: undefined
  }
]
[main 2022-03-11T09:17:40.112Z] windowsManager#doOpenEmpty {
  restore: true,
  remoteAuthority: undefined,
  filesToOpen: undefined,
  forceNewWindow: true
}
[main 2022-03-11T09:17:40.114Z] IPC Object URL: Registered new channel vscode:8545fbe1-8a0c-492d-a867-18b5f52c266a.
[main 2022-03-11T09:17:40.114Z] window#validateWindowState: validating window state on 1 display(s) { mode: 1, x: 346, y: 195, width: 1024, height: 768 }
[main 2022-03-11T09:17:40.114Z] window#validateWindowState: 1 monitor working area { x: 0, y: 0, width: 1280, height: 720 }
[main 2022-03-11T09:17:40.115Z] window#ctor: using window state { mode: 1, x: 346, y: 195, width: 1024, height: 720 }
[34319:0311/101740.116186:ERROR:cursor_loader.cc(116)] Failed to load a platform cursor of type kNull
[0311/101740.161550:ERROR:directory_reader_posix.cc(42)] opendir /home/tim/.config/Code - Insiders/Crashpad/attachments/bc3c5bed-d8cc-462c-a527-32b5c3354908: No such file or directory (2)
[1]    34319 segmentation fault (core dumped)  /usr/share/code-insiders/code-insiders  --ozone-platform=wayland --verbose

EDIT: May be a different bug, since this happens also on Gnome Wayland

If so, https://github.com/microsoft/vscode/pull/145527 is the PR for upgradation to electron 18. Will have to wait for another month.

For sway users on archlinux: There is a hidpi version of sway-git on the aur that allows scaling of the xwayland frame which avoids blurriness if you use integer scale for sway to begin with. You will need to use Xdefaults or Xresources in that case to fix vscode’s scaling.

I think this issue should be fixed in Electron v18.0.1 or v17.3.1, since the main branch is on 17.3.0 the update to 17.3.1 should be a no brainer.

Still present in Arch Linux/sway-1.7/wlroots-0.15.0 + VSCode-1.64

Any news or work arounds one might be able apply to get this working?

🎉 Fixed in the latests insiders code-insider-x64-1649156657

Are you on Gnome? You need to change vscode settings to use custom titlebar.

NVM! Just fixed by running code-insiders --enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland

Are you on Gnome? You need to change vscode settings to use custom titlebar.

The new version (1.66.0) doesn’t launch for me. I am using sway. Now it’s showing the same error as https://github.com/microsoft/vscode/issues/141964#issuecomment-1064923453

bumping electron to the latest 13.x release with the backport’d fix got stuff working again…

but with vscode moving to electron v16 looks like we’re now waiting for https://github.com/electron/electron/pull/32603 to ship in a later release