Arch Linux

It does not seems to be any electron user, but actually code. I could not reproduce with the packages I have.

In any case this has very likely been introduced by the change for  FS#74034 . I bet that if you reverse https://github.com/archlinux/svntogit-community/commit/f1bc01d61ed2f713efdc6d33104600e0f79ada10#diff-a9d028136db20390534ea297df670ab599022de8dcb57c1b71fd4913d7a1f7d7 in /usr/bin/electron18, it should work again.

I’m not sure what the best path here. Maybe the code launcher behaviour should be investigated and improved.

Can confirm, it works by reversing the /usr/bin/electron18 file.

By reverting the patch it launches but Electron/Code still complains: Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.

That happened before as well, I think that is emitted by code.

Ok, it works

Code now depends on electron19 which also has the same issue.

Including code PM's to also take a look.

Dupe  FS#75783 

The issue is ELECTRON_RUN_AS_NODE=1 in the /usr/bin/code script. The flags get probably processed in a different code path that rejects --ozone-platform-hint=auto as invalid.

I don't even know why that variable was set in the script, and I am leaning towards just removing it but does anyone know more about why it might be needed?

This env var makes all flags be passed straight to Node.js, bypassing Electron. To me, it seems fine to remove it; I also don't see why it is needed.

Looks like the fix prevents the crash of code but now code doesn't read the flag at all.

I used --ozone-platform-hint=auto in electron19-flags.conf file. It didn't work. But directly passing it via shell works.

Passing the flag on the command line instead of in the electron19-flags.conf file only changes the order of the arguments.

`code --ozone-platform-hint=auto` executes `exec /usr/lib/electron19/electron /usr/lib/code/out/cli.js /usr/lib/code/code.js --ozone-platform-hint=auto`

`code` with `--ozone-platform-hint=auto` in the config file executes `exec /usr/lib/electron19/electron --ozone-platform-hint=auto /usr/lib/code/out/cli.js /usr/lib/code/code.js`

The order of the arguments configured in the flags file is controlled by the electron script and there is nothing I can change in code to fix that. You can use `~/.config/code-flags.conf` though and it should put the flags at the end of the command.

Putting the flag at the end causes this `Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.` so it seems to me like it would actually be correct to put it in electron19-flags.conf rather than in code-flags.conf

I can confirm that putting flags in `code-flags.conf` works (producing a warning, though) while in `electron19-flags.conf` does not. Seems like the latter file is ignored by vscode.

It is not ignored, the command executed is exactly the one I mentioned over here.

You can test this is the case by changing `/usr/bin/electron19` so that the first line is `#!/usr/bin/bash -x`

I would really want the flag in electron19-flags.conf so that all electron applications can use the same flag.

Why is that code does not pick up the flag but bitwarden picks the flag?

I get the same behavior with Electron 20. Please add it to the title as well.

Another dupe  FS#76483  (or at least closely related)

> I don't even know why that variable was set in the script, and I am leaning towards just removing it but does anyone know more about why it might be needed?

CLI commands, as per the above linked issue, they are currently broken.

@mtorromeo

Could the ELECTRON_RUN_AS_NODE=1 variable be added back for the time being?

It is necessary as per upstream (see linked issue) and it breaks my Ansible deployment playbooks when it is missing.