Hi Spork,

2018-02-09 23:29 GMT+01:00 Spork Schivago <sporkschiv...@gmail.com>:

> Hello,
> I'm running a fresh install of CentOS 7, fully updated, with the epel and
> google repositories added to my repo list.
> yum info gvfs.x86_64 shows
>  Version 1.30.4
>  Release 3.el7
> This package provides gvfsd and the backends, including gvfsd-admin.   I
> noticed a typo in the man-page for gvfsd while I was trying to trouble
> shoot a problem I'm having and thought I should mention that first, in case
> it's not fixed in the latest upstream release.   I see the following text
> in the man-page for gvfsd:
> ...
>  It spawns new backends when requested and keeps track fo their lifecycle,
>  maintaining a list of active mounts and creates direct connections to
>  them.
> ...
> I believe 'keeps track fo their lifecycle' should actually read 'keeps
> track of their lifecycle'.

Thanks for the patch, you have already provided...

> My main problem is when I try to use the gvfsd-admin backend, it fails.
>  For example, in Nautilus, I hit CTRL-L and type admin:///root   and
> eventually, it times out.    Same with gedit.
> I've even tried using gio list admin:///root
> I followed the debugging instructions located at:
> https://wiki.gnome.org/Projects/gvfs/debugging
> And every time I try to access a directory or file using the admin-backend
> (which I believe gvfsd should be starting automatically), I see the
> following message:

Yes, it should be automounted.

> Refusing to render service to dead parents.

I have never seen such error and I don't have any idea currently what might
be its source.

> I've reached out to the CentOS 7 forum members to see if they could
> possibly reproduce the error, but I haven't received a response yet and I'm
> not sure how to continue.    Would anyone know what I might be doing wrong
> here?
> As a temporary work-around, I create a Gnome auto-start file that executes
> a bash script that executes:
>  pkexec /usr/libexec/gvfsd-admin --address $DBUS_SESSION_BUS_ADDRESS

That's it is not definitely right way to do, but might work...

> And this allows me to successfully use the backend.   dmesg shows:
> 42094.083046] fuse init (API version 7.22)
> [42098.844999] warning: `gvfsd-admin' uses 32-bit capabilities (legacy
> support in use)
> But I don't think gvfsd-admin using 32-bit capabilities is causing my
> issue.    Any suggestions?

Yes, this is not probably the issue here..

> I apologize if this is the wrong place to ask.   The mailing list page
> said:
> This list is about development and use of gvfs, a virtual filesystem
> implementation for gio.
> So to me, because this involves the use of gvfs, and it's backends, I
> thought it was the perfect place to get help.

Yes, this is perfect place :-)

Let me try in RHEL 7 first and I will then let you know...


Ondrej Holy
Software Engineer, Core Desktop Development
Red Hat Czech s.r.o
gvfs-list mailing list

Reply via email to