~/.config/autostart/mattermost.desktop is created and filled with the necessary Exec line to launch mattermost
Observed behavior
~/.config/autostart/electron.desktop is created with Exec=/usr/lib/electron31/electron --hidden
Log Output
No relevant log output
Additional Information
There are apparently many instances of people encountering the behavior where Electron launches in dev mode and decides that app.name is Electron, which then seems to confuse auto-launch's efforts to figure out how to set up the autostart script.
Checks before filing an issue
Mattermost Desktop Version
Version 5.10.0-develop.1 commit: 139fc347
Operating System
EndeavourOS Linux current x64
Mattermost Server Version
Mattermost Version: 10.2.0
Steps to reproduce
Expected behavior
~/.config/autostart/mattermost.desktop
is created and filled with the necessary Exec line to launch mattermostObserved behavior
~/.config/autostart/electron.desktop
is created withExec=/usr/lib/electron31/electron --hidden
Log Output
Additional Information
There are apparently many instances of people encountering the behavior where Electron launches in dev mode and decides that
app.name
is Electron, which then seems to confuseauto-launch
's efforts to figure out how to set up the autostart script.https://github.com/electron-userland/electron-webpack/issues/239 https://github.com/electron-react-boilerplate/electron-react-boilerplate/issues/2197 https://github.com/quasarframework/quasar/discussions/11044 https://github.com/SimulatedGREG/electron-vue/issues/424
I've created https://github.com/Teamwork/node-auto-launch/issues/131 upstream but suspect this is going to be an issue between MM and Electron.