gvfsd-sftp hangs at 100% cpu on sonnecting to some servers

[sam tygier]

Binary package hint: gvfs

When connecting to some ssh servers through the connect to server screen in gnome, gvfsd-sftp hangs at 100% cpu indefinitly. this is on ubuntu hardy running from the 20080328 livecd.

after a ~10 mins the attempt times out. i get a dialog (i removed the hostname)
"Can't display 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."

the gvfsd-sftp process continues to use 100% cpu

with other servers it works fine.
not working servers are running Scientific linux 3 and 4. working server is running ubuntu gutsy.
i can connect to all the servers with the ssh command, using passwords for authentication.
i have tried both from the same LAN and over the internet.

I will attach the verbose output from connecting to the 2 servers from the command line.

[sam tygier (samtygier)]

seems to be fixed with the latest gvfs (or something has changed on the servers i am loging into)

[jenom (jenom)]

New information.

[jenom (jenom)]

I just stumbled across this bug myself and I found the cause. The gvfsd-sftp uses sftp to connect to the server. I tried to connect directly this sftp but with no success. The error reported was "Received message too long $NUMBER". Further investigations revealed it was a problem with the severs shell configuration. For the sftp on ubuntu uses ssh to connect to the server on some shells text is emitted to the console (Something like "Hello..." or whatever even if it is a non-interactive session). This causes the error above with sftp. In my case I had "screen -r" in my shell option without checking if the session was interactive. After correcting this, sftp worked fine and so did gvfsd-sftp. No more 100% CPU after this correction. It's still a bug obviously.

cheers
jo

[gulfuroth (gulfuroth)]

I'm having the same problem with Ubuntu 9.04. Package vers gvfs-backends 1.1.7-0ubuntu1
No clues why and who is launhing it, tough :(. Will do some research on it.

Daniel

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

[francoiscn (francois-c-n)]

I've had the same bug on a few of my SSH sessions and found out that for all of them where I had this specific issue it was because in one of my sourced SETUP.bash (in .bashrc on the remote server) there was an echo line.

For example:

in my .bashrc I would have the following:

    source /home/ilt/SETUP.bash

and in /home/ilt/SETUP.bash

I would have:

    echo 'hello 123'

Removing the echo line fixes the problem.

[Sebastien Bacher (seb128)]

the new issue is a different one and a configuration bug don't reopen this bug

[Marat Dyatko (marat-dyatko)]

gvfsd-sftp took 74.8% of CPU

[Marat Dyatko (marat-dyatko)]

Ubuntu Lucid 10.04 Alpha 3

[Macarena (marcoaasilva)]

Affects me on Ubuntu Lucid 10.04 Beta 1

[Sebastien Bacher (seb128)]

the lucid issues are rather bug #530605

[thecure (keith-k)]

Had this before but somehow was fixed for awhile now when ever "Backups" running scheduled backup gvfs-sftp 100% cpu. Client and server. Client ubuntu 14.10 64bit and server 14.10 64bit server. What logs could I provide to assist with this bug?

[thecure (keith-k)]

Forgot to mention with backup completes both machines show 100% usage. I forgot how to umount the sftp share and since it doesnt show in nautilus when Backups making connection have to kill or restart.