I guess this will need a pretty porous sandbox :stuck_out_tongue:
Nautilus uses
"finish-args": [
"--share=ipc", "--socket=x11",
"--socket=wayland",
"--talk-name=org.gnome.OnlineAccounts",
"--talk-name=org.freedesktop.Tracker1",
"--filesystem=host",
"--talk-name=org.gtk.vfs", "--talk-name=org.gtk.vfs.*",
"--talk-name=ca.desrt.dconf", "--env=DCONF_USER_CONFIG_DIR=.config/dconf"
],
But Dolphin has more restrictive access to the filesystem for some reason
"finish-args": [ "--device=dri",
"--share=ipc",
"--share=network",
"--socket=x11",
"--socket=wayland",
"--filesystem=home",
"--filesystem=/run/media",
"--talk-name=org.kde.kiod5",
"--talk-name=org.kde.JobViewServer",
"--talk-name=org.kde.kpasswdserver",
"--system-talk-name=org.freedesktop.UDisks2" ],
I tend to prefer the dolphin implementation over nautilus here
I tend to prefer the dolphin implementation over nautilus here
Yeah, well we don't really get a choice 馃槢
Dolphin's seems more restrictive because it uses the KIO bus. KIO is a daemon which essentially provides a file manager backend and Dolphin is just the user interface to that.
In theory, you can do that to some extent with gvfs, but I don't find it particularly weird that a file manager would ask for permissions to access the entire filesystem.
Most helpful comment
Yeah, well we don't really get a choice 馃槢
Dolphin's seems more restrictive because it uses the KIO bus. KIO is a daemon which essentially provides a file manager backend and Dolphin is just the user interface to that.
In theory, you can do that to some extent with gvfs, but I don't find it particularly weird that a file manager would ask for permissions to access the entire filesystem.