@ BloodyIron It looks like the problem you are experiencing is the same
issue as I have had.  I think the reason that it works after you kill
gvfsd-smb-browse is that your FreeNAS server is advertising itself via
mDNS, and gvfsd will see that.  You don't need SMB1 or WSDD for gvfsd to
discover your NAS.  But it is also looking for a "Windows Network" (i.e.
the Windows "network neighborhood" or workgroup that shows up as a
separate subfolder) using SMB1, and that fails if the server does not
provide SMB1.  Crucially, however, it fails in a way that leaves the
gvfsd-smb-browse process in a bad state where it fails to allow browsing
of the server even though it has been discovered via mDNS.  I encourage
you to take a look at my patch, or to use the PPA at
patch. It does indeed look like there is a bug here in that attempting
discovery via SMB1 somehow breaks browsing of the server discovered via

See also my remarks here:

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (1881780).

  gvfs can't list shares from smb servers that disabled SMB1

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to