New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracker for applications using --filesystem=xdg-run/gvfs #2180
Comments
Used to generate flathub/flathub#2180
GNOME Videos ( |
|
Please be careful, if the application doesn't talk directly to gvfs, there's no need to add that hole. Eg. Krita doesn't need the change... |
Here is a complete list of apps with `--talk-name=org.gtk.vfs.*`, maybe it helps
|
I'm fairly certain most of them don't need to talk to gvfs... |
Cozy doesn't need the change: DejaDup doesn't need the change: Handbrake fixed in flathub/fr.handbrake.ghb@b5ac0a5 FreeCAD, timetrack, Daty, trenchboom, blastem, itopia, and thincast don't need the change. |
org.gimp.GIMP//stable is done |
- add gvfsd permissions: see flathub/flathub#2180
org.inkscape.Inkscape//stable is done. |
(We also found that |
- add gvfsd permissions: see flathub/flathub#2180
com.rawtherapee.RawTherapee is done. |
Fixed in baobab: flathub/org.gnome.baobab#5 |
Fixed in Password Safe: flathub/org.gnome.PasswordSafe#9 |
I forgot to mention I did org.gnome.OCRFeeder during an update. |
Need for gvfs >= 1.48. See: flathub/flathub#2180.
Need for gvfs >= 1.48. See: flathub/flathub#2180.
Pinta fixed. |
This documents the changes being tracked on Flathub at: flathub/flathub#2180
I've added documentation at https://docs.flatpak.org/en/latest/sandbox-permissions.html#gvfs-access if anyone if still curious about the options. |
This should make it possible to access GVfs resources with backend URIs. One example is the admin backend using the admin:// URI. References: - https://docs.flatpak.org/en/latest/sandbox-permissions.html#gvfs-access - flathub/flathub#2180 - https://wiki.gnome.org/Projects/gvfs/backends
This should make it possible to access GVfs resources with backend URIs. One example is the admin backend using the admin:// URI. References: - https://docs.flatpak.org/en/latest/sandbox-permissions.html#gvfs-access - flathub/flathub#2180 - https://wiki.gnome.org/Projects/gvfs/backends
Maybe worth editing the description of this issue? |
- Add dri permission: `libEGL warning: wayland-egl: could not open /dev/dri/renderD128 (No such file or directory)`
- Add dri permission: `libEGL warning: wayland-egl: could not open /dev/dri/renderD128 (No such file or directory)`
Flatpak documentation: https://docs.flatpak.org/en/latest/sandbox-permissions.html#gvfs-access
Starting with gvfs 1.48, GNOME gvfs daemons will use an on-disk socket to communicate with
gvfsd
so that it will be possible to talk to gvfs while disabling the network. However, for applications to be able to talk through that on-disk socket, they need to be able to access it.If your application talks directly to gvfs daemon, for example to list mounts, and access optical discs, then you will need to modify your application's manifest to include access to the
$XDG_RUNTIME_DIR/gvfsd
. For example, for a JSON manifest:If your application doesn't need to talk to gvfs via D-Bus, then it doesn't need access to
xdg-run/gvfsd
.If you tried to access files using gvfs, and
gvfsd
was inaccessible, this error would be returned:The text was updated successfully, but these errors were encountered: