xdg-desktop-portal VS flatpak

>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)

Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.

No, it looks like you have to do it on an application basis.

https://github.com/flatpak/flatpak/issues/2913

Flatpak

> CLI tools do not implement auto-complete themselves. What you are seeing are auto-complete scripts for your shell that make network connections.

nit: This is incorrect. Robust auto-complete scripts call the actual program to provide completions.

That is what Flatpak does. It is Flatpak itself that makes the network connections.

https://github.com/flatpak/flatpak/blob/main/completion/flat...

Not that it would make any differencen if it was implemented in Bash seeing as the Bash script is also provided by Flatpak.

The only performance impact I know of is with the seccomp filter in CPU-bound tasks: https://github.com/flatpak/flatpak/issues/4187

Skimming through the recent comments, there might be a way to optimize some of it.