Comment 4 for bug 1958670

I've temporarily reverted it back to the 1.7 behaviour of using an in-process GTK file picker. This is being rolled out to all users now.

I would really like to keep using the portals, they do provide significant benefits in allowing access to the entire file system, rather than just a subset of $HOME (by default; although in the Pinta snap you could also add /mnt and /media by giving it the correct permissions manually, and similarly Flatpak can give more fine grained control still). They also provide nicer integration for KDE users.

But until this critical file loss bug is sorted out this seems to be the only respectable choice.

I can agree with the behaviour you've mentioned of seeing the /run folder appear in UI's being confusing. I wonder if this is because they never anticipated people to make use of the save as functionality more than once per file. Personally, I'm tempted to say the benefits provided by the portals outweigh that one UI flaw, but it might be possible to fix it on the Pinta side. It won't appear in the latest revision though.

If you wish to patch ASAP, run
> sudo snap refresh
Otherwise, the majority of users end up updated quite rapidly too with the automatic update process.

Meanwhile, I'll keep an eye out on the feedback of this bug in the forums, because again, it's quite possibly effecting far more than just Pinta. And the Flatpak should really consider disabling the portals for now too, although I'm unsure if it exhibits the same behaviour, I'd say there's a significant probability it does.