Ondrej Holy 2e38753aed flatpak: Add --share=network to fix synchronous gvfs connections ... GVfs communicates with daemons over abstract sockets. Currently, synchronous GIO API doesn't work for GVfs locations, because abstract sockets seem to be blocked by sandbox permissions. This is not problem in most cases as Nautilus uses asynchronous API usually. But this breaks e.g. "Empty Trash" functionality as it is for some reason based on synchronous API. In order to fix this problems, it is necessary to allow access to sockets beginning with `unix:abstract=/dbus-vfs-daemon/socket-`, but I am not aware of better way than adding `--share=network`, which allows access to all abstract sockets: http://docs.flatpak.org/en/latest/sandbox-permissions-reference.html#f2 Just a note that it is not clear to me, why it affects only the synchronous API as the asynchronous API also uses abstract sockets. See the corresponding Flatpak bug: https://github.com/flatpak/flatpak/issues/2711		2019-03-13 08:47:04 +00:00
..
gcovr.json	Replacing gcovr module with gcovr.json	2018-11-20 14:02:20 +00:00
org.gnome.Nautilus.json	org.gnome.Nautilus.json: Fix tracker options	2019-02-17 21:21:11 +00:00
org.gnome.Nautilus.yml	flatpak: Add --share=network to fix synchronous gvfs connections	2019-03-13 08:47:04 +00:00
org.gnome.NautilusGtk4.yml	flatpak: Add --share=network to fix synchronous gvfs connections	2019-03-13 08:47:04 +00:00
org.gnome.NautilusMaster.yml	flatpak: Add --share=network to fix synchronous gvfs connections	2019-03-13 08:47:04 +00:00