Skip to content
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

Closed
rpete3 opened this issue Oct 24, 2023 · 5 comments · Fixed by #2518
Closed

Autostart is not working with flatpak install #2517

rpete3 opened this issue Oct 24, 2023 · 5 comments · Fixed by #2518
Labels

Comments

@rpete3
Copy link

rpete3 commented Oct 24, 2023

Autostart is not working with flatpak install

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Preferences'
  2. Click on 'autostart' checkbox
  3. reboot
  4. CopyQ does not start automatically and ~/.config/autostart does not have an entry for copyq

Expected behavior
CopyQ should start automatically.

Version, OS and Environment

  • Application Version 6
  • OS Ubuntu 22.04.3 LTS
  • Desktop environment, Gnome shell 42.9
@rpete3 rpete3 added the bug label Oct 24, 2023
@hluk
Copy link
Owner

hluk commented Oct 25, 2023

Maybe the reason is that I removed --filesystem=xdg-config/autostart:create from the flatpak spec (last year). I think it was because the linter complained: flathub/com.github.hluk.copyq@480fb36

@hluk
Copy link
Owner

hluk commented Oct 25, 2023

Maybe the reason is that I removed --filesystem=xdg-config/autostart:create from the flatpak spec (last year). I think it was because the linter complained: flathub/com.github.hluk.copyq@480fb36

Yup, that's the reason. All works if I start the flatpak app with the following command:

flatpak run --filesystem=xdg-config/autostart:create com.github.hluk.copyq

Let me try to revert the change in the spec file.

@hluk
Copy link
Owner

hluk commented Oct 25, 2023

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

hluk added a commit that referenced this issue Oct 25, 2023
Autostart option should not be available for example for flatpack apps
since it is handled by a background portal.

Fixes #2517
hluk added a commit that referenced this issue Oct 25, 2023
Autostart option should not be available for example for flatpack apps
since it is handled by a background portal.

Fixes #2517
@rpete3
Copy link
Author

rpete3 commented Oct 25, 2023

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/flatpak-builder-lint#87

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.

@hluk
Copy link
Owner

hluk commented Oct 25, 2023

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/flatpak-builder-lint#87

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 ~/.config/autostart/ anyway due to the linter not accepting the spec with --filesystem=xdg-config/autostart:create before building the flatpak.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants