Flatpak Limitations
Trying to track what issue we still have with Flatpak
- Display/open folder of current image xdg-desktop-portal#475
- Partially able to work around via
--filesystem=host
- Partially able to work around via
- Move through images in folder xdg-desktop-portal#463
- Partially able to work around via
--filesystem=host
- Partially able to work around via
- Opening files from GVfs xdg-desktop-portal#102
- SMB, SFTP etc
Trash://
- Workaround via complete GVfs access
- Adding opened images to "Recent" xdg-desktop-portal#215
- No workaround available.
- Not able to (un)trash files glib#845
- Workaround via complete GVfs access and
--filesystem=host
- Workaround via complete GVfs access and
- Not able to drag and drop folders into Loupe xdg-desktop-portal#911
-
gtk::FileLauncher
requires a file, making it impossible to use it on sources that are not available as files in the Flatpak- Workaround via also giving the legacy access to GVfs
--filesystem=xdg-run/gvfs
- Workaround via also giving the legacy access to GVfs
- Glycin decoders spawned by loupe are kept around when loupe does not terminate cleanly. Reportedly, this might also happen in other situations. The processes are listed as background processes in GNOME Shell. The details of the listing depend on the GNOME Shell version.
- No workaround available.
- There is no equivalent of
bwrap --ro-bind
available in Flatpak, making it possible to expose the parent folder of SVGs to the sandbox spawned viaflatpak-spawn
. Therefore, external content will be missing from SVGs.- No workaround available.
Issues caused elsewhere
- Printing requires confirming the print dialog twice. This is caused by missing GTK support.
- Workaround by keeping the PrintOperation around. Probably has a proper solution with new PrintDialog API.
Upcoming problems
- Overwriting files without being able to write in the directory
- Usual way is to write first and then move. Using
/tmp/
for that is not an option since it's not guaranteed to be on the same partition/remote drive/etc.
- Usual way is to write first and then move. Using
Edited by Sophie Herold