Description of problem:
I have a couple of machines on my LAN that I routinely connect to via Nautilus: one is a Buffalo Linkstation NAS that exposes itself in various ways, as an SMB Windows share but also via AFP; the other is an old machine still running Fedora 14 that I connect to with SSH (SFTP). When I installed Fedora 20 on my new laptop I connected to it in the usual way (browse network, double-click server, double-click share, authenticate and in you go). All works fine, but if you suspend the laptop and then go back to Files on resume, Nautilus has hung - seems as though it is hung waiting for a mount to respond? That's a guess, I don't know what data you'd need to verify this, but happy to supply it. For now I will connect to one protocol at a time and see if I can narrow it down to a specific mount that's causing the issue.
Version-Release number of selected component (if applicable):
For me this happens every time I forget to unmount the mounts I use frequently, but as yet I haven't isolated a specific mount or protocol.
Steps to Reproduce:
1. Open Files in GNOME3 and connect to a few network drives (in my case, there was an AFP mount, a SFTP mount and, occasionally, a SMB mount too);
2. Browse around, make sure they are all connected and working as expected;
3. Suspend your computer and leave it for a while;
4. Resume the computer and go back to Files.
Files will have frozen and it won't recover.
Files continues without issue and doesn't hang, if network shares have been disconnected they gracefully drop off.
I'm going to close this as a dupe, because after more testing I narrowed it down to the AFP protocol specifically (samba and ssh seem stable) and I found the referenced report, which is pretty much what I'm seeing. Seems it appears in Ubuntu too, so it's probably upstream in gvfs, specifically gvfsd-afp.
*** This bug has been marked as a duplicate of bug 1001320 ***