Comment 82 for bug 1778322

Bionic desktop verification

With gvfs-backends from the release pocket:
ubuntu@bionic-desktop:~$ apt-cache policy gvfs-backends
gvfs-backends:
  Installed: 1.36.1-0ubuntu1.3
  Candidate: 1.36.1-0ubuntu1.3
  Version table:
 *** 1.36.1-0ubuntu1.3 500
        500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages

I get an empty "windows network" tab in the desktop (see attached screenshot empty-windows-network-before-test.png).

After updating to this package from proposed:
  Version table:
 *** 1.36.1-0ubuntu1.3.2 500
        500 http://br.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages

And logging out and back in, I get a populated windows network tab (see screenshot populated-windows-network-after-test.png).

I can then connect to the pub share on localhost (see screenshot connecting-to-pub-after-test.png) and, once that is done, smbstatus shows this output:
ubuntu@bionic-desktop:~$ sudo smbstatus

Samba version 4.7.6-Ubuntu
PID Username Group Machine Protocol Version Encryption Signing
----------------------------------------------------------------------------------------------------------------------------------------
3771 nobody nogroup bionic-desktop (ipv4:192.168.122.213:56026) NT1 - -
3874 ubuntu ubuntu 192.168.122.213 (ipv4:192.168.122.213:32800) SMB3_11 - partial(AES-128-CMAC)
3807 nobody nogroup bionic-desktop (ipv4:192.168.122.213:56028) NT1 - -
3762 nobody nogroup bionic-desktop (ipv4:192.168.122.213:56022) NT1 - -

Service pid Machine Connected at Encryption Signing
---------------------------------------------------------------------------------------------
IPC$ 3762 bionic-desktop Fri Jun 21 21:07:33 2019 UTC - -
IPC$ 3807 bionic-desktop Fri Jun 21 21:08:09 2019 UTC - -
IPC$ 3771 bionic-desktop Fri Jun 21 21:07:37 2019 UTC - -
pub 3874 192.168.122.213 Fri Jun 21 21:08:30 2019 UTC - -

No locked files

The connection to the pub share is using SMB3_11.

The connections using NT1 show why https://bugs.launchpad.net/gvfs/+bug/1828107 is still relevant, but it's a separate bug. See comment #55 for my reasoning. I think releasing this update is a step in the right direction.

Bionic verification succeeded.