Still present in 14.04 when copying files from ym raspberry pi.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/220696
Title:
Connection to SSH via file browser disconnects
To manage notifications
ran into this bug today. Ubuntu 12.04 up to date. Nautilus to a tablet,
local network, via the wifi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/220696
Title:
Connection to SSH via file browser
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.
--
You received this
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
This is reproducible on Lucid as well.
--
Connection to SSH via file browser disconnects
https://bugs.launchpad.net/bugs/220696
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
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.
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
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'
