-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AppImage : Default path detection doesn't work properly because it uses mount path #89
Comments
erichs
pushed a commit
to erichs/stethoscope-app
that referenced
this issue
Mar 7, 2019
per Teamwork/node-auto-launch#89, this resolves the desktop autostart path to the executable, which defaulted to current working path of the running process. Due to the AppImage architecture, that default doesn't work cleanly and requires override.
rmcvey
pushed a commit
to Netflix-Skunkworks/stethoscope-app
that referenced
this issue
Mar 7, 2019
per Teamwork/node-auto-launch#89, this resolves the desktop autostart path to the executable, which defaulted to current working path of the running process. Due to the AppImage architecture, that default doesn't work cleanly and requires override.
Please see that we're looking for contributors / maintainers: #64. I'm happy to give access to people who are willing to help improve things, merge pull-requests, close issues, etc. |
Oxalin
changed the title
Default
AppImage : Default path detection doesn't work properly because it uses mount path
Dec 6, 2023
options.path
doesn't work with electron & AppImage
This should be fixed by #91 |
Feel free to give feedback |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
node -v
): 10.11.0I'm packaging my Electron app as AppImage for Linux, and the auto-launch puts the
process.execPath
to created desktop entry, which looks like/tmp/.mount-myapp-des20NgDd/my-app
. The .mount-... dir is temporary so it doesn't work with auto-launch.Workaround is to pass
{path: process.env.APPIMAGE}
to AutoLaunch.The text was updated successfully, but these errors were encountered: