Arch Linux

Description:
The "Start automatically after system login" preference just brings up the Electron window (same as when you just run electron without an app) after login rather than element.

Additional info:
* package version(s): element-desktop-1.7.14-1 element-web-1.7.14-1 electron-10.1.5-1
* link to upstream bug report, if any: https://github.com/vector-im/element-web/issues/15943

Steps to reproduce:

* Settings, Preferences, General, "Start automatically after system login"
* System logout, login (or check the autostart file mentioned below)

I expect element to start, presumably minimised / in the status bar.
Instead I just get the electron window.

Element is started using KDE, presumably the element-desktop command, which runs:

electron /usr/lib/element/app.asar "$@"

When the option is ticked, it creates ~/.config/autostart/electron.desktop containing:

[Desktop Entry]
Type=Application
Version=1.0
Name=electron
Comment=electronstartup script
Exec=/usr/lib/electron/electron --hidden
StartupNotify=false
Terminal=false

It appears to be directly caused by the use of a common element between apps in ArchLinux.

See the following comment in the upstream report for a potential solution:
https://github.com/vector-im/element-web/issues/15943#issuecomment-745436886
> Yeah, Arch likes to keep one copy of electron instead of all apps bringing their own.
>
> Judging from your research, a solution from the Arch side would be to patch src/electron-main.js so that the two AutoLaunch constructor's option objects include path: /usr/bin/element-desktop. I don't see a neat way to fix this from the node-auto-launch side.