desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #59818
[Bug 745556] Re: nautilus ssh connection after suspend to ram - browsing location lost
Just saying, this thing is not fixed.
Atm, what I see mostly happen:
I wake up from suspend-to-ram with 4 nautilus tabs open to an ssh location.
These are unresponsive, until I unmount the dead ssh connection. I try browsing them to a local folder, but they do not respond.
When I do this, the tabs just close.
This means, I cannot easily interrupt my work on ssh with suspend or
hibernate.
There are several solutions imaginable for this.
- On the dead ssh connection, in addition to "unmount", there could be a "reconnect" or "restore connection" option.
- Unresponsive nautilus tabs, that depend on a dead ssh connection, could have a reconnect/unmount button.
- Unmounting the ssh connection would still close all those tabs.
I think, the same would make sense for external storage devices. Think of external HD, that gets disconnected from power supply during suspend / hibernate.
When they are removed / unmounted in a controlled fashion, then the nautilus tabs can close.
When they are removed / switched off during suspend or hibernate, and then just missing, the nautilus tabs should remain in a "pending" state, with a note asking to reconnect the device.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/745556
Title:
nautilus ssh connection after suspend to ram - browsing location lost
Status in “nautilus” package in Ubuntu:
Incomplete
Bug description:
10.04 LTS - the Lucid Lynx
Following steps:
1. Places > Bookmarks > "ssh on server xyz"
(that's a bookmark I made in a remote folder)
2. I type the password to open the nautilus window with the remote folder.
3. Ctrl-T to open two other nautilus tabs in different remote folders on the same ssh connection. Navigate around in all three tabs, but stay on the remote server.
4. Open one of the remote files in gedit.
5. Suspend to RAM.
6. Wake up from Suspend.
Now we are in a strange situation:
- The gedit remote file looks like it is still open, but doing anything in there makes the gedit tab unresponsive.
- All three nautilus tabs look like they are still open, but they are unresponsive.
The only way to fix it:
7. Unmount the ssh connection (in the nautilus side pane)
(btw, left-clicking it makes the side pane scroll state jump down)
Now all but one of the remote nautilus tabs is being closed, and instead we get one nautilus tab in a local location.
The file in gedit is still open.
Now we can either
8.a) Save the file in gedit -> asks me for the ssh password, and the ssh connection is back. (but nautilus location is still lost) Or
8.b) Hit "Back" in nautilus -> asks me for the ssh password, the ssh connection is back, and the nautilus location is restored - for one of the tabs. The other tabs are still closed, the location lost.
8.c) Use again the bookmark to get to the remote location.
Now the problem is, the other two tabs are lost, and I need to navigate again to get to these locations.
So,
9. Ctrl-T to open two other Nautilus tabs. Navigate around until we are back at the locations where we have been.
To summarize, the problems are:
- Having to click around more than necessary to reconnect the ssh connection.
- Having to navigate again to get back to the folders, instead of them being remembered.
Thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/745556/+subscriptions