STILL having this problem! Also, the gnome issue of #506 is NOT RELEVANT! As this issue PREDATED WSD IN TOTALITY.
Like, how more clear do I REEAALLLYYYY need to make this? I kill the gvfsd-smb-browse process, and IMMEDIATELY I can browse SMB shares when SMB1 is disabled. CLEARLY the application is capable, however is unwilling to cooperate until it gets restarted (gvfsd-smb-browse). This has NOTHING to do with WSD in impact, or even as a solution! WSD _IS NOT PRESENT ON MY NETWORK_.
STILL having this problem! Also, the gnome issue of #506 is NOT RELEVANT! As this issue PREDATED WSD IN TOTALITY.
Like, how more clear do I REEAALLLYYYY need to make this? I kill the gvfsd-smb-browse process, and IMMEDIATELY I can browse SMB shares when SMB1 is disabled. CLEARLY the application is capable, however is unwilling to cooperate until it gets restarted (gvfsd-smb-browse). This has NOTHING to do with WSD in impact, or even as a solution! WSD _IS NOT PRESENT ON MY NETWORK_.
Hell, we even have another thread _claiming_ that this was fixed in much earlier versions of Ubuntu (which clearly it wasn't): https:/ /bugs.launchpad .net/ubuntu/ +source/ gvfs/+bug/ 1778322
Again, also, _THIS HAPPENS OUT OF THE BOX FOR ALL UBUNTU DESKTOP INSTALLATIONS CURRENT AND FOR THE PAST 4+ YEARS_.