However you can do a print-to-file, but the output seems to be placed into the containers file-system, so it cannot be accessed. For me a workaround to this was to run Evolution with access to the users /home file system enabled:
flatpak run --filesystem=home org.gnome.Evolution
I was wondering if this shouldn’t be a usual sandbox permission for Evolution or if there is a security reason it is not enabled?
I can’t believe it but this seems still an issue as of today on Silverblue! Seriously? How exactly is one supposed to print anything to a PDF file? Well, I can do it but the resulting file is hidden inside that container/sandbox stuff! Come on!
You do realise, that we are talking about exporting/printing to a PDF file, do you? I can print to my sister’s physical printer as well, that is not the problem.