-
Notifications
You must be signed in to change notification settings - Fork 3
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
Support linux appimage #2
Comments
The problem I see in creating an auto launch for AppImage is that the path to the AppImage can be changed anytime. What I think we can do is something like this: The user opens the AppImage this generate the autorun entry but if later the user change the location of the AppImage the autorun entry will be invalid, but once the user reopen the app using the AppImage the autorun entry will be updated with the new location. |
Yes, because the path changes whenever the mount is done (reboot), the previously registered path is invalid. How about passing
This works as expected, but the user needs to pass the AppImage file path manually, And if the file path is changed by the user, the entry file will be invalid. (So I'm not sure this is the right way though) |
Hi, I have the same message auto launching my app (https://github.com/uparlange/bing-wallpaper) with Windows 11. It is working good with Windows 10 and MacOS (BigSur and Monterey). |
Hello @Izurii, |
@Izurii, the condition should be added here: easy-auto-launch/src/easy-auto-launch.ts Line 122 in cec445c
Many thanks for this cleaner architecture! |
I'll be taking a look at that asap. Thank you for bringing a solution to this old bug :) |
node -v
): 12.22.1On Windows, and on Macos, easy-auto-launch works well.
But on Ubuntu using
Appimage
, easy-auto-launch launch below the screen (Electron) instead of my app.I think maybe the below issue, PR in the original repo could be related to this issue.
Thanks for remaking the awesome library!
The text was updated successfully, but these errors were encountered: