Axios what the other ppl where trying to do is give the sandbox system access but for that it should use the portal.
exactly, I appreciate you reading
my links--they were full of clues or ways to get closer to solution.. these patches/workarounds, none permanent, always revolve round opening the closed pipe, jacking things like "an UNIX socket in $XDG_RUNTIME_DIR/kpxc_server " that are way over my head. ***your last link----I was shocked Flathub had literature that addresses this---involves that same manifsest/config file workarounds way over my skill level.
Axios ppl have same problem when they start trying to make a browser more secure after awhile they wonder why nothing works.
this is a very interesting correlation and correct in many case. you can install the extension umatrix which cripples every website in some way til you learn how to use it...pick your poison I guess. or about:config
fanatics are out there on the nets.
Thanks for seeing this and making the connections to the 'remedies' or thinking about this as far as a fix.
From your first link: "With Flatpak, each application is built and run in an isolated environment, which is called the ‘sandbox’. Each sandbox contains an application and its runtime. By default, the application can only access the contents of its sandbox. Access to user files, network, graphics sockets, subsystems on the bus and devices have to be explicitly granted. Access to other things, such as other processes, is deliberately not possible. By necessity, some resources that are inside the sandbox need to be exposed outside, to be used by the host system. These are known as ‘exports’, since they are files that are exported out of the sandbox, and include things like the application’s .desktop file and icon."
I bolded the important stuff. that 'export' business is at the half-hypothetical stage and way above my skills best I can see.
Great observations. KeepassXC was great while it lasted. Maybe that 'portal' my flatpak browser had with keepassxc native app was magical and accidental and completely became borked 2-3 weeks ago with a system update. It's Occams Razor explanation and it's no shade on Solus:
those apps were never supposed to talk to each other to begin with...........