xdg-desktop-portal VS Flatseal

>Not losing all the work every time your windows manager crashes

https://news.ycombinator.com/item?id=37509703

>remapping keys

>Use xinput to change parameters of their input devices (libinput dropped most configuration options present with evdev)

Up to the compositor.

>Global shortcuts

Also up to the compositor. Was added to xdp in https://github.com/flatpak/xdg-desktop-portal/blob/main/data... so it's up to the compositor's xdp impl to provide it. It was created by a KDE dev so I assume KDE implements it at least.

>tunnelling over ssh

https://gitlab.freedesktop.org/mstoeckl/waypipe

> - O proper screen recording support

Works just fine. I use OBS.

> - broken screen sharing

Never had any trouble with it.

> - No proper global keyboard shortcut

> - No push to talk support

On its way: https://github.com/flatpak/xdg-desktop-portal/pull/711 / https://flatpak.github.io/xdg-desktop-portal/#gdbus-org.free...

> - Several problems with multiple screens

Haven't had any more than on X11, but then again I do use Nvidia hardware on Linux.

It might help, but at this point Linux containers can't really stabilize the whole environment, especially for games. Particular pain points include accelerated graphics (which theoretically can have a stable kernel interface, but in practice is so complex and performance-sensitive that it's not stable enough to be a "reference platform", so to speak) and modern game controllers (which present a whole mess of concerns typically "addressed" in Flatpak by granting the device=all permission and hoping for the best [1]).

I also know a guy who ran into issues with a kernel update breaking a custom allocator, although I don't know the fine details. That wasn't for a game, but games also use custom allocators for various reasons.

[1] https://github.com/flatpak/xdg-desktop-portal/issues/536

I don't use Wayland, but it seems xdg-desktop-portal since 1.16.0 has a 'Global Shortcuts portal'. Perhaps check it out.

https://github.com/flatpak/xdg-desktop-portal

It's being discussed: https://github.com/flatpak/xdg-desktop-portal/issues/611

The first bug report was filed in early 2022 but unfortunately no progress yet on the matter, even after numerous similar reports ever since.

Yeah been having the same issue since I changed to using the unstable branch, supposedly noticed and fixed upstream for a few variants of the problem (different people with different configurations of DE and xdg-* deps installed report the same issue due to timeouts of the other portals)

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