Yes. It was like windows positioning, one of the things that do not function that way anymore
Basically, the proper way would be adding libportal to dependencies. It is what allows proper access to autostart through: https://libportal.org/flags.BackgroundFlags.html

And then:

-Keep the old way, but punch a hole in the sandbox to keep access to autostart (--filesystem=xdg-config/autostart:create), else you get How to run this app automatically on startup, without showing the full GUI? #80
-having permission to set autostart from the get go , and using libportal to enable it (I dont recall the exact manifest permission, but the code itself is straightforward)
-have libportal request to the user permission to enable autostart (Its the same code. Just one line less in manifest. User gets a notification from the system and go Allow or Deny. In Appcenter guidelines it needs to show after Badger main window)
-not adding libportal, and telling the user "you can add to autostart here" with a link to switchboard preferences.

The last one is what i did with Jorts https://github.com/ellie-commons/Jorts in the preferences
After quick discussion with Danielle, who said it was more in line with the standards. The portal allows to add or remove autostart, but not checking the current state, so adding both buttons and no toggle instead felt too awkward

However you would need to do a choice which one you prefer
The old way + sandbox hole may also raise some security concerns because it pretty much is a venue a malicious app would try to gain access to, because it allows to run a command outside a sandbox. (I doubt it would pass the flathub submission process for example. Its not explicit on appcenter guidelines, but i dont think Danielle would say nothing)

Doesn't autostart on login #87

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions