Connection to SSH via file browser disconnects

[PRab]

1. I connect to a server by clicking Places -> Connect to Server -> Select "Service type" == "SSH, enter Server (nova.kettering.edu) and User Name.
2. I open a terminal and type "ssh <email address hidden>".
3. I close the terminal.
4. When I try to browse the server (via Places menu) I receive an error: "Couldn't display "sftp://<email address hidden>/". Error: Internal error: The underlying ssh process died. Please select another viewer and try again."

Note: It does not fail 100% of the time. I think it has something to do with how long I am logged onto the server for.

I am using Hardy Heron RC.

[Henri Cook (henricook)]

I am also affected by this issue (changed to confirm)

Is there some sort of default timeout, or failure to act on nautilus' part to keep the connection active and renewed OR renew it when the user tries to continue browsing? Surely either of these actions are preferred to the 'ssh process died' message and forcing the user to log back in again

[Cyberkilla (cyberkilla04uk-deactivatedaccount)]

I get almost identical messages. I'm running Jaunty.

Steps for me to get this error:
- Mount a remote server via SSH, as explained in the bug report.
- Hibernate/suspend computer for the night.
- Resume in the morning and notice that the nautilus windows showing the remote folder closes itself when I attempt to use it. In fact, it also closes if I attempt to save a file on the remote server (already opened in gedit before hibernation).

The message is the same as above. "underlying ssh process died".
Clicking the bookmark under Places on the menu will bring it back, but I have to browse to the directory and open my tabs again, which is what annoys me.

I had assumed that mounting a remote computer would be transparent to the user, with gvfs attempting to reconnect/smooth over connection problems behind the scenes; mounted until the user specifically chooses to unmount it.

As I said, this was just an assumption - it seems to be the standard behavior for local mounts though. Can anyone shed some light on this?

Thanks in advance.

[Craig (candrews-integralblue)]

It's even easier to reproduce than having to suspend/hibernate or disconnect the network... just wait. If the SSH process is idle for a bit (on my SSH server it's around 10 minutes) the SSH server will disconnect the client. gvfs should automatically reconnect, but instead it gives this error.

(BTW, I've confirmed this behavior on Jaunty and Karmic)

[Sune Keller (sune-keller)]

This is reproducible on Lucid as well.

[donquixote (lemon-head-bw)]

Lucid.

For me it doesn't crash, it just freezes.
1. Open nautilus ssh, click some remote files to open in gedit.
2. Hibernate, wake up.
3. Try to edit one of the remote files opened in gedit.
-> gedit freeze.

Solution (for now):
4. In Nautilus, unmount the ssh connection. (and copy the location before doing it!)
-> gedit becomes responsive again.

Now you can choose one of two solutions:

5a. edit and save a file in gedit (just add a space and delete it again)
-> gedit will ask for a password, and reconnect. I can continue my work, yeah.

5b. Ctrl-l in Nautilus, paste the ssh location from clipboard, go.
-> Nautilus will ask for a password, and reconnect. I can continue my work, yeah.

------

This is still better than what I remember from Windows (with WinSCP and putty), but still far from ideal.
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/605283

[Ville Ranki (ville-ranki)]

This still happens in Natty:
1) connect to sftp share
2)suspend & resume
3) Internal error: The underlying ssh process died

I doubt that anything will be done for this bug. It's already been in confirmed state for 3 years. Maybe it should be filed in Gnome bugzilla also.

[Aldian (aldian-gp)]

ran into this bug today. Ubuntu 12.04 up to date. Nautilus to a tablet, local network, via the wifi

[Sam Castledine (samuel-castledine)]

Still present in 14.04 when copying files from ym raspberry pi.