5 ms·

The closest thing to a solution is to blame the distros for shipping the apps incorrectly and encouraging users to do unsupported things like combining several

The closest thing to a solution is to blame the distros for shipping the apps incorrectly and encouraging users to do unsupported things like combining several apps from several different desktops together without testing them, when this has never really been a thing that ever worked correctly. The correct way to get portal support is to use the flatpak versions of those packages, because those are the only packages that have actually been designed and tested to work with the portal. And if you are a person who really does not like flatpak, then you should ask your distro to start integrating sandboxing and portals into their own package managers and testing/supporting the packages that way.

ginko 4y ago
Flatpak? Are you serious?
- Crysstalis 4y ago
  I am not sure what you are asking, other than asking for me to repeat myself. I gave the reason why Flatpak is the only option here.
ducktective 4y ago
The Correct Way™ is actually NixOS/GuiX these days. I had major issues when I used Snap GUI apps. Like it was not clear where did the config file saved to or sometimes the file picker couldn't even detect my drives (due to sandboxing). It was doing its own thing regarding theming. If Flatpak is anything like this, then it's not a viable solution.
- neurostimulant 4y ago
  > sometimes the file picker couldn't even detect my drives (due to sandboxing) At least you can use `flatpak override` command to whitelist access to certain path.
- Crysstalis 4y ago
  I do not believe NixOS or Guix are shipping these packages with a sandbox that uses the portals, but I could be wrong. I am not sure of anything about Snap, I have never used it. In Flatpak, all the config files are saved to ~/.var/app/. The portal should be able to handle exposing a file from the host, but the app has to be built to use the portal correctly. You can have themes but you must install the flatpak package for them, pulling themes from the host environment is a security issue because technically themes are equivalent to doing code injection.

ginko 4y ago

Flatpak? Are you serious?

Crysstalis 4y ago
I am not sure what you are asking, other than asking for me to repeat myself. I gave the reason why Flatpak is the only option here.

ducktective 4y ago

The Correct Way™ is actually NixOS/GuiX these days. I had major issues when I used Snap GUI apps. Like it was not clear where did the config file saved to or sometimes the file picker couldn't even detect my drives (due to sandboxing). It was doing its own thing regarding theming. If Flatpak is anything like this, then it's not a viable solution.

neurostimulant 4y ago
> sometimes the file picker couldn't even detect my drives (due to sandboxing) At least you can use `flatpak override` command to whitelist access to certain path.
Crysstalis 4y ago
I do not believe NixOS or Guix are shipping these packages with a sandbox that uses the portals, but I could be wrong. I am not sure of anything about Snap, I have never used it. In Flatpak, all the config files are saved to ~/.var/app/. The portal should be able to handle exposing a file from the host, but the app has to be built to use the portal correctly. You can have themes but you must install the flatpak package for them, pulling themes from the host environment is a security issue because technically themes are equivalent to doing code injection.