Hi Cameron, I'm just wondering if you'd happened to have tested with portals 1.18/Ubuntu 23.10 to confirm if the problem still exists there? (I would myself, but I mostly work with Linux in virtual machines and 23.10 seems to just crash everytime I try it on HyperV).
Of course the problem is that the Flatpak/Snap will run on distributions that don't have this fix, and I'd rather not recommend people use PPA's to backport the functionality (nor could I even find one).
But if it does work, and presuming we could probe the version in use to see if it has this fix, I'd propose:
The Open File interface likely doesn't need touching, but defaulting to $HOME (or $SNAP_REAL_HOME for snap at least) might be a decent idea anyway, but isn't relevant for us here.
The Save File interface is a lot more problematic, but assuming we can identify the portals in use, either:
1) force the folder to open at $HOME, since the main point of using "Save As" is to create a new copy elsewhere, this isn't too unreasonable an assumption to make (and certainly better than `/run`)
2) Do nothing if the portals are new enough to to avoid the problem, in theory feeding the `/run` path back into FileChooser should actually work fine without changes.
Hi Cameron, I'm just wondering if you'd happened to have tested with portals 1.18/Ubuntu 23.10 to confirm if the problem still exists there? (I would myself, but I mostly work with Linux in virtual machines and 23.10 seems to just crash everytime I try it on HyperV).
In theory, https:/ /github. com/flatpak/ xdg-desktop- portal/ pull/1007/ files should have fixed this for us.
Of course the problem is that the Flatpak/Snap will run on distributions that don't have this fix, and I'd rather not recommend people use PPA's to backport the functionality (nor could I even find one).
But if it does work, and presuming we could probe the version in use to see if it has this fix, I'd propose:
The Open File interface likely doesn't need touching, but defaulting to $HOME (or $SNAP_REAL_HOME for snap at least) might be a decent idea anyway, but isn't relevant for us here.
The Save File interface is a lot more problematic, but assuming we can identify the portals in use, either:
1) force the folder to open at $HOME, since the main point of using "Save As" is to create a new copy elsewhere, this isn't too unreasonable an assumption to make (and certainly better than `/run`)
2) Do nothing if the portals are new enough to to avoid the problem, in theory feeding the `/run` path back into FileChooser should actually work fine without changes.