FS#75783 - [code] Fails to launch if flags are set in Electron configuration

Attached to Project: Community Packages
Opened by Daniel Playfair Cal (hedgepigdaniel) - Saturday, 03 September 2022, 13:48 GMT
Last edited by Toolybird (Toolybird) - Sunday, 04 September 2022, 01:00 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: When Electron flags are configured in `electron19-flags.conf`, VSCode does not launch.

Instead it logs errors such as:
```
/usr/lib/electron19/electron: bad option: --ozone-platform-hint=auto
```

This is is despite such flags being valid, and a command such as `electron --ozone-platform-hint=auto` working without issue. It happens for VSCode because `code.sh` sets `ELECTRON_RUN_AS_NODE=1` before running Electron, which prevents Electron from accepting flags.

I suspect this has been broken since https://bugs.archlinux.org/task/74034 - previously the configured Electron flags were passed to VSCode rather than directly to Electron.


Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 04 September 2022, 01:00 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#75667 
Comment by Daniel Playfair Cal (hedgepigdaniel) - Saturday, 03 September 2022, 13:50 GMT
Reproduced with:
* electron 20.0.3-1
* code 1.71.0-1

And with ~/.config/electron19-flags.conf containing:
```
--ozone-platform-hint=auto
```

Loading...