-
Notifications
You must be signed in to change notification settings - Fork 15
Autostart #94
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 #94
Conversation
Thanks again. General GitHub tip: avoid making your changes to the fork's main branch. Create a separate branch instead, like you did here. Saves a lot of trouble. |
Okay, so how do I test this? I checked out the branch, built and installed with flatpak-builder, then opened the window normally. It started doing its thing, but didn't ask for an autostart permission. I rebooted the machine, and still nothing. I'm probably missing something? Is there something to configure? Sorry, I'm new to portals. |
Make sure Badger is stopped Build this branch
you will see a "Requesting autostart" in the terminal at some point is there a badger ? Likely, it does not ask, because we gave it permission in the past - I see in the eOS settings, the flag for autostart is set. Which is why there is no popup Im not sure how we could ask for Pantheon to "forget" and ask like the first time around. But for total first time users it should show. Same in gnome-shell. Alternatively we can add the permission in the manifest, so this never ever becomes a topic |
Ah okay, got it. Let me test it in the evening. 🙌 |
Hmm, you're right, it didn't ask. And people will likely be confused about it stopping. Let me look up how the permission works. |
The manifest entry to have control ootb would be
we would be getting flak for it for a flathub release (these people are quite rigid), and comments at best from the appcenter reviewer (we could try, though) we could also explain in the UI that people need to add background permission (and link to it), and/or have a button to do the requesting but it could fail/get denied immediately/fail and show a dialog explaining why also the UI is minimal, theres not really a place to put anything related to permissions/autostart (maybe divide in two tabs? Scales/Settings) I dont have a solution. I feel like thats a big ass element for the future of the app that you need to decide. |
The background portal docs do specify an option to specify user-visible I think we should just try the manifest entry. This is the exact use case the portal exists to serve. We'll deal with any concerns that arise. |
Yeah and also the app is open source so people can tell theres nothing shady, just a lil critter I have no clue how to test this because toggling off background permission is telling pantheon explicitly to disallow Badger and i suppose Pantheon has priority over the manifest. I may also copy 1:1 this approach for Reminduck which im also trying to port |
Okay, I'll test this again, maybe from a separate user and then we should be good to go. |
Sorry for the delay. I tested this from a fresh account on my system, but strangely, it still doesn't ask for permission to autoload. So it's not that Pantheon "remembers" things from a past life, it's just how it deals with the flag. |
Did you revert it to before i added the permission in the manifest? |
I tried with that as well on a fresh user, but still doesn't ask. 😕 Do you know of any other way? |
No. I dont. Theres no plumbing either because apps arent supposed to control that. |
Yeah, this is gnarlier than we thought. I'll try and dig deeper on this. |
The toggle to disable reminders is literally the first thing user see
Thats like negligible |
We could also have the toggle be the one setting/removing thr flag |
Running in the background and consuming a small amount of memory by keeping the flag on isn't an issue. The issue is that it doesn't actually autostart. So across sessions, the user needs to launch it manually despite the flag being on and the item showing up in Startup settings. That's what I'm trying to wrap my head around. |
It doesn't ? Shit i thought the issue was the asking part. I thought the ability to run without windows still worked ?? Else we could just do it the old way and add permission to . config/autostart... My god why is this so complicated ?? Its a very small app with like five tog 67E6 gles! |
Headless mode still works if manually started yes ? |
It does, yes. I was also considering going back to the old autostart script. This looks like one of those rare cases where the hack works better than the standards. 😄 |
I tried the old way of installing an autostart .desktop file, but now flatpak creates its own sandboxed directories so even that doesn't work. 🫠 😭 |
Did you put in permission for that folder |
Oh. My bad. Another reason to fix my currently multi-planetary sleep cycle. 🙃 |
gkhtrrthbktr take care of yourself man Let us know if we should do this or anything (though Stellas frustrated about this thing) |
@teamcons Thank you for the support. You've been amazingly patient on this one. I am planning to spend some time on Sunday to close this for good, but do share any guidance/pointers/gotchas. You know a lot more than me about how this stuff works in 2025. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As a long-haired English dude said in the 16th century, much ado about nothing.
What |
Fixes #87,
this is the proper one
i am struggling with git - never had to do multi branch drifting before