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 doesn't work #18

Closed
Bleuzen opened this issue Aug 18, 2018 · 7 comments
Closed

Autostart doesn't work #18

Bleuzen opened this issue Aug 18, 2018 · 7 comments

Comments

@Bleuzen
Copy link

Bleuzen commented Aug 18, 2018

PulseEffects has this nice option to "Start Service at Login".
But when I toggle it on with the flatpak version, it creates the autostart file in
~/.var/app/com.github.wwmm.pulseeffects/config/autostart
instead of
~/.config/autostart

Flatpak should have access to the real autostart directory to create the file there instead of in ~/.var.

Also within the autostart file,
Exec=pulseeffects --gapplication-service
has to be replaced with
Exec=com.github.wwmm.pulseeffects --gapplication-service

@TingPing
Copy link
Member

Yea it can't work, you'll just have to manually add it for now.

There is discussion about Flatpak exposing this but no work has been done on it.

@wwmm
Copy link
Collaborator

wwmm commented Aug 18, 2018

The Exec=com.github.wwmm.pulseeffects --gapplication-service will require changes in PE sources. At this moment the exec field is hardcoded. It would be necessary to patch PE sources before building

@AsavarTzeth
Copy link
Collaborator

I don't see a point in trying to workaround this issue right now. Instead we need a proper autostart portal. See issue: flatpak/flatpak#118

Also read the comments in that issue as for why I cannot use --filesystem=xdg-config/autostart to grant access to the app itself.

For now it would probably be best to have a build time option for enabling/disabling this (and hiding it from the gui).

One might also document the limitation in the help files, and/or wiki and suggest how it can be done manually.

@iQmam0n
Copy link

iQmam0n commented Aug 31, 2018

I was able to start with the following change.
~/.config/autostart/pulseeffects-service.desktop

from:
Exec=pulseeffects --gapplication-service
to:
Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=pulseeffects com.github.wwmm.pulseeffects --gapplication-service

@AsavarTzeth
Copy link
Collaborator

@iQmamOn Yes that is how you add it manually, for now.

@vchernin
Copy link
Collaborator

This is fixed in EasyEffects, successor to PulseEffects. I have no plans to try to backport the fix here, I think solving flatpak/xdg-desktop-portal#579 is a better use of time as that means the background portal could be used on the host.

@1player
Copy link

1player commented Jun 22, 2022

This can be closed, I've been using EasyEffects with autostart for months and it's never failed me.

@wwmm wwmm closed this as completed Jun 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants