Today's fun discovery: apparently, if you install the #FreeCAD Flatpak and try to use the OpenSCAD workbench, you _cannot_ give it a Flatpak-installed OpenSCAD. Literally impossible, even if you nuclear Flatseal permit it everything, because by default, it can neither see the export directory of Flatpak nor the Flatpak binary itself, which it needs to run said export.
How the idea that someone might want a working OpenSCAD workbench in a Flatpak FreeCAD didn't occur to the packager, I dunno.
@koz This is bad on the part of the packager but also good on the part of the isolation system that applications can't see each other unless you explicitly let them.
@dalias I have no objection to sandboxing of this kind by default - it is a sensible default and should stay that way. However, there is _no way whatsoever_ I can see to allow this to work. I've tried blanket-enabling _every_ filesystem permission in Flatseal, and even adding /var/lib _manually_, and _still_ it fails.
@dalias Oh, for extra joy - a globally-installed OpenSCAD won't work either, even with aforementioned nuclear permit-all Flatseal settings.
Great, now I have to figure out how I'm going to do this simple-seeming task in _Blender_, because apparently competence, FreeCAD and Flatpak live in different realities.
