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 file made in flatpak version of desktop app uses wrong command #2716

Open
queenbiscuit311 opened this issue Apr 9, 2024 · 0 comments
Labels
Fixed Internally Issue has been fixed, but fix has not yet been released

Comments

@queenbiscuit311
Copy link

queenbiscuit311 commented Apr 9, 2024

When enabling "Launch on Startup" on the bluebubbles desktop flatpak, the following file is made in ~/.config/autostart:

[Desktop Entry]
Type=Application
Name=bluebubbles
Comment=bluebubbles startup script
Exec=/app/bluebubbles/bluebubbles [minimized]
StartupNotify=false
Terminal=false

The exec line here seems to be what the app thinks its path is in the flatpak container, but since the app needs to be launched outside of that container, this won't work. The actual file file that would be needed to accomplish opening the app at startup is this:

[Desktop Entry]
Type=Application
Name=bluebubbles
Comment=bluebubbles startup script
Exec=flatpak run app.bluebubbles.BlueBubbles [minimized]
StartupNotify=false
Terminal=false

The app would probably need to detect if it's running in flatpak and change the autostart file accordingly.

jjoelj added a commit that referenced this issue May 17, 2024
Signed-off-by: Joel Jothiprakasam <hijoelj@gmail.com>
@jjoelj jjoelj added the Fixed Internally Issue has been fixed, but fix has not yet been released label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed Internally Issue has been fixed, but fix has not yet been released
Projects
None yet
Development

No branches or pull requests

2 participants