Skip to content

[Feature request]: Autostart for Flatpaks #1652

@Zinkelburger

Description

@Zinkelburger

Version

  • I'm using version 1.18.0

Existing requests

  • I've checked Existing requests

Advanced Preferences

  • I've checked Advanced Preferences

What operating system are you using?

Linux

Operating System Version

Fedora 42, Aurora

Problem description

Autostart doesn't work when its in a flatpak, especially on an immutable OS like Aurora.

This has been noted in #1517

Possible solution

I'd like to use Flatpak Portals to request the program starts at login

This is documented in Background Portals

I have an implementation with Claude. But to test it, I need to package it as a Flatpak, instead of just npm run dev


I have significant issues using the flatpak-builder command, trying to use the manifest at net.hovancik.Stretchly

  1. Issue with generated-sources. So I copy package-lock.json from the main stretchly repo & rebuild generated sources with the flatpak-node-generator
  2. Update manifest from node20 to node22 which Stretchly now uses
  3. Esbuild binary error (no idea how to resolve, been trying to add things to the manifest but it doesn't help)
    Error: ENOENT: no such file or directory, stat '/run/build/stretchly/flatpak-node/cache/esbuild/bin/esbuild-current'

Sorry if any of this was incorrect. I'd appreciate any help. Thanks for this program 🙂

Alternative solutions

I'm pretty sure the only way out of a Flatpak is with the portals

Additional information

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions