gvfsd doesn't start gvfsd-admin when needed.
Posted: 2018/02/08 23:43:24
From the man pages of gvfsd, I see:
So to me, I take this to mean that gvfsd is responsible for starting the backends, when requested. Is this correct?
On my system, if I start a program like Nautilus or Gedit and try to use the admin backend by opening a file or directory using the admin:// prefix, gvfsd does not start gvfsd-admin and eventually, the process times out. With GEdit, I get an error message stating that the admin:///<filename> couldn't be opened.
With Nautilus, it'll open an empty window and the task bar at the bottom of my screen shows Loading....and then just disappears after a while and nothing happens.
If I manually start gvfsd-admin:
where unix:abstract=/tmp/dbus-.... is the DBUS session address, then I can open files / directories using the admin:// prefix.
I'm trying to figure out if there's a bug in gvfsd, or if there's a configuration option somewhere I need to change to enable the gvfsd-admin backend, or if my security settings are somehow blocking gvfsd from starting the gvfsd-admin backend.
Also, there's a typo in the man page. If copied and pasted directly from the man page. I believe the statement:
should actually read:
(the word of has the letters reversed)
Thanks.
Code: Select all
...
The primary task of gvfsd is to act as a mount tracker/manager. It spawns new backends when requested and keeps track fo their lifecycle, maintaining a list of active mounts and creates direct connections to them.
...
On my system, if I start a program like Nautilus or Gedit and try to use the admin backend by opening a file or directory using the admin:// prefix, gvfsd does not start gvfsd-admin and eventually, the process times out. With GEdit, I get an error message stating that the admin:///<filename> couldn't be opened.
With Nautilus, it'll open an empty window and the task bar at the bottom of my screen shows Loading....and then just disappears after a while and nothing happens.
If I manually start gvfsd-admin:
Code: Select all
pkexec /usr/libexec/gvfsd-admin --address unix:abstract=/tmp/dbus-J2bNTl2MbU
I'm trying to figure out if there's a bug in gvfsd, or if there's a configuration option somewhere I need to change to enable the gvfsd-admin backend, or if my security settings are somehow blocking gvfsd from starting the gvfsd-admin backend.
Also, there's a typo in the man page. If copied and pasted directly from the man page. I believe the statement:
Code: Select all
...keeps track fo their lifecycle....
Code: Select all
...keeps track of their lifecycle...
Thanks.