sftp freezes nautilus after standby / resume cycle
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gvfs (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Hello, I have been having this problem for at least six months. I often use the 'connect to server' > 'sftp://<email address hidden>' in nautilus to transfer files to and from remote servers. It works great. The problem comes from suspending / resuming near the time of doing these actions. (I am about 90% sure)
If the error occurrs, after resuming, nautilus will freeze, and I can end it, and then it will not re launch again. In terminal , the error it gives when trying to launch is. "Could not register the application: Timeout was reached" Launching a nautilus instance with sudo works as expected.
I have determined that the error comes from the sftp daemon because I have found, through trial and error, that ending a specific SSH process will unfreeze / allow relaunching of nautilus almost instantly after it is killed.
$ ps -aef | grep ssh >>
paul 5731 20771 0 09:47 pts/26 00:00:00 /usr/bin/ssh -oForwardX11 no -oForwardAgent no -oPermitLocalCo
this is an example of that the process looks like that is causing the hang.
This error occurs even if I make sure to close nautilus before putting the computer to sleep.
*update*
I also realize today that this bug is even bigger then I thought at first. I had been having an issue in the past where I would try to save files from programs such as gedit and as soon as I press ctrl+s gedit would just freeze and I had lost my work a few times. I just today found that instead of this being a gedit problem, it is a problem with this nautilus ssh connection, as engine the SSH process mentioned above also unfreezes the program. I assume similar problems with saving or opening from other programs may be related!
Information:
Distributor ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty
32 bit
Hardware:
Ibm / lenovo thinkpad T60, ati fireGL board.
4gb ram
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.