Date: Fri, 16 Oct 2020 13:51:27 +0400 From: Gleb Popov <arrowd@freebsd.org> To: Christoph Moench-Tegeder <cmt@burggraben.net> Cc: Jonathan Chen <jonc@chen.org.nz>, FreeBSD ports list <freebsd-ports@freebsd.org>, freebsd-gnome@freebsd.org Subject: Re: gvfs delay on login? Message-ID: <CALH631=dM5CXQzcn%2Bn8vARToA85mM8X7XGv-LPoe2LGr8JPVNg@mail.gmail.com> In-Reply-To: <20201016094547.GA32427@elch.exwg.net> References: <CAJuc1zO=hiFE8P6gS=27j=FoSv0FQeia9aCV=y9VfgzsKa=0aQ@mail.gmail.com> <20201016094547.GA32427@elch.exwg.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 16, 2020 at 1:45 PM Christoph Moench-Tegeder <cmt@burggraben.net>
wrote:
> Hi,
>
> ## Jonathan Chen (jonc@chen.org.nz):
>
> > I recently updated my ports, and with the update of gvfs-1.46_1, I'm
> > noticing a 20s delay when I log in with mate-session. The closest
> > indication as to what may be the problem is in one of my logs:
> >
> > ** Message: 15:35:14.744: Initializing gksu extension...
> > Error creating proxy: Error calling StartServiceByName for
> > org.gtk.vfs.GoaVolumeMonitor: Timeout was reached (g-io-error-quark,
> > 24)
>
> Yes, that's the problem. The most basic workaround is to build
> gvfs without option GOA ("Gnome Online Accounts"), that's what
> I did (I don't use mate and don't have that specific login problem,
> but a lot of other stuff shows related troube, timouts, failures, ...).
>
> The real fix would be to figure out how to get the required dbus
> services running - gvfs source provides some systemd units, which
> are not that helpful for us (obvious reasons, yeah).
>
It is sufficient to provide service files to enable D-Bus autostart
functionality:
https://foss.heptapod.net/bsdutils/bsdisks/-/blob/branch/default/org.freedesktop.UDisks2.service.in
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALH631=dM5CXQzcn%2Bn8vARToA85mM8X7XGv-LPoe2LGr8JPVNg>