Comment 5 for bug 1677467

Part of the problem seems to be that a location mounted this way does not appear to Files to need a network connection to be accessed - it is just part of the local file system. Moreover the location remains mounted by the system when the network connection is broken. So Files will attempt to load it. I find that the tab eventually times out and Files interface is not blocked meanwhile (which is the expected behaviour). However, I also find that trying to load a home folder tab is also blocked until the mount tab times out and then the home folder tab also times out, which is unexpected. Other locations, not below the home folder can be displayed normally.

I'll see if anything can be done to mitigate this.