Flatseal VS freedesktop-sdk

And not only that, the idea of portals is, IMO, misguided. See this view/bugreport when a flatseal user understands that even though they restricted permissions to access a certain area, the flatpak, itself, can ask to open files there and if OK'd that will be allowed. Their expectation is that with the overrides say "no access" it means "no access even if the flatpak asks very nicely". https://github.com/tchx84/Flatseal/issues/196

Since you installed the programme via Flatpak, you should simply lack the necessary rights (https://docs.flatpak.org/en/latest/sandbox-permissions.html). You can extend the rights quite easily with https://github.com/tchx84/flatseal.

Yes, filed https://github.com/tchx84/Flatseal/issues/196 a while ago, got no joy.

One design feature than can turn into an issue in some scenarios (usually dev tools) is the permissions of a flatpak. In case I need to tweak things, I use Flatseal. I know you can manually do this from the command line but I don’t change permissions that often so I don’t bother learning how to do that.

Does the Flatpak Permissions Settings replace a tool like Flatseal?

What about flatseal then ? https://github.com/tchx84/Flatseal

https://github.com/tchx84/Flatseal (Also on Discover. For security reasons, the Discover store installs apps as sandboxed "flatpak" apps. This one is used to view what each up can do and change the permissions of apps. May be required if the sandboxing breaks something, though usually not required.)

I believe it does. As an example if I try running Godot from the Steam flatpak, it won't be able to see any of the contents of my ~/Projects folder unless I explicitly allow the steam flatpak access to that directory that via flatpak's CLI options or using Flatseal

I think I might have confused two unrelated posts. The one that references Polar Signals is this one:

https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/...

So not a perf issue there, but they don't think the workflow is suitable for whole-system profiling. Perf issues were in the context of `perf` using DWARF:

https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/issues/...

But the fd-sdk https://gitlab.com/freedesktop-sdk/freedesktop-sdk and gnome build meta https://gitlab.gnome.org/GNOME/gnome-build-meta projects can prove as good references.

With all of these hypothetical features out of the way and looking just at current release software, Flatpak allows you to do so much stuff that isn't accessible for a not-so-techy user. Custom installation folder? Yep. Running mesa-git GPU drivers? You got it. Any way to easily do this via GUI? In typical Linux fashion, nope. For a GUI focused packaging format this is a big letdown.

Link to (official?) how-to: https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/wikis/Mesa-git

You can load up Mesa GIT using environment variables, see here. Honestly what I miss the most from flatpak Steam is properly working non-Steam shortcuts, but I've given up on that.

It was my understanding that the packages for vaapi are just put into the -extra version of the sdk so app maintainers can opt out, but they are still available if they want to use them. See https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/10616