com.skype.Client VS flatpak

Screen sharing seems to be a difficult problem to resolve. Zoom only just resolved this recently[1], Webex has been promising a fix for a while[2], and Skype still hasn't done anything[3].

[1] https://support.zoom.us/hc/en-us/articles/6634039380877-Zoom...

[2] https://help.webex.com/en-us/article/9vstcdb/Webex-App-for-L...

[3] https://github.com/flathub/com.skype.Client/issues/142

If the device still works in the os and just not in skype. I would try the flatpak package. https://flathub.org/apps/details/com.skype.Client

https://snapcraft.io/skype or Flatpak https://flathub.org/apps/details/com.skype.Client

I also found some old issue on Github Latest version of Skype won't run #70

Alternatively one can use the Flatpak packaged Skype.

I have no idea if that is true or not, I haven't used Skype for more than a decade. But, an app running as a Flatpak can't directly create files in /etc/ even if that directory was exposed in the sandbox (which it isn't in the Skype flatpak, as you can see here), just like any other process running as a non-root user can't create files in /etc/ (unless your permissions on /etc/ are severely messed up). So if what you claim is true, it has nothing to do with Flatpak's sandbox or with portals. And since in the default configuration the pulseaudio daemon (which is running outside the sandbox) does not run as root either, I severly doubt that what you claim here is true at all.

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.