-
Notifications
You must be signed in to change notification settings - Fork 462
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
Autostart is not working with flatpak install #2517
Comments
Maybe the reason is that I removed |
Yup, that's the reason. All works if I start the flatpak app with the following command:
Let me try to revert the change in the spec file. |
So the linter still doesn't allow me to use this. I think what it means is that it should not be handled by the application itself: flathub-infra/flatpak-builder-lint#87 |
Autostart option should not be available for example for flatpack apps since it is handled by a background portal. Fixes #2517
Autostart option should not be available for example for flatpack apps since it is handled by a background portal. Fixes #2517
So you are telling me we can’t use the preferences in CopyQ to activate autostart? The recommended way is to pass the —filesystem option to create it? That’s not very user friendly. |
The recommended way seems to be to configure the autostart in your desktop environment (for example: https://code.whatever.social/questions/64444987/how-can-i-set-a-flatpak-application-to-run-on-startup). I'm not very familiar with all this, but I cannot now configure the flatpak app to access |
Autostart is not working with flatpak install
To Reproduce
Steps to reproduce the behavior:
Expected behavior
CopyQ should start automatically.
Version, OS and Environment
The text was updated successfully, but these errors were encountered: