Comment 4 for bug 208450

Revision history for this message
jenom (jenom) wrote :

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