@nixCraft
And it runs shitily on all of them. Flathub packages have the stupidest of bugs all of the time.
Like one app asking you to select your texteditor application to open a file with but you can't find it in the filesystem cause that app doesn't see that path in the filesystem.
Or it showing Gnome GUI instead of KDE GUI because it was packaged only with the GNOME ones.
Or it having been packaged with a vulnerable library version even though the one on the system has been patched...
@agowa338 @nixCraft if developers packaged their software in this way, then it is what it is. They are not paid apps and developers make their software mostly in their free time.
Ah and about the first issue, you can change flatpak permission to allow it to access your home directory, so your apps can open whatever file in the home directory you want.
Doesn't help when App A wants to open a file with App B (or better prompts the user to select an App B for opening that file with) when App B is in /usr/bin and that flatpack overlays it and hides that app...
Point being Flatpacks are just a huge waste of time. Literally everything I tried to install via flatpack I later had to reinstall from the repos because of poor integration.
Also default permissions are a joke...
I want it to just work properly without stupid bugs. Basically I want it to work as promised. Because the way they are is just annoying...
The example I'm talking about is e.g. FreeCAD in a flatpack and then you try to open a text file within the project and then it fails to open the file as it can't find kwrite to open it...
Or the GUI just visually not fitting in as it is packaged using the gnome libraries instead of the KDE ones...