I haven't thoroughly tracked what messages I see now, but it certainly seems much better.
I do now get that ""Opps something went wrong." message about "the underlying SSh process died", and I can then just try again, whereas before I had to explicitly kill a process. I don't know for sure if that's never necessary any more, but I'll report here if I experience it. Even if killing the process is still sometimes necessary, things do seem much better, though obviously the "Oops something went wrong message" doesn't need to be shown to the user if a reconnection can be done without even mentioning it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/377322 Title: Nautilus sftp connection breaks spontaneously after a while, needing re-login to fix it Status in GVFS: New Status in “gvfs” package in Ubuntu: Incomplete Bug description: When I have used an sftp connection for a while - started from Places/Connect to Server or from a bookmark - it breaks, typically after an hour or so. The only way to get an sftp connection to that server again is to re login to my computer. The error message I get is Could not open location 'sftp://......' DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken Sometimes when this happens, my computer freezes for about 60 seconds. I have Ubuntu 9.04 64 bits - error happened on Hardy also - on a computer with an AMD64 processor. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/377322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
