Cannot access files using sftp

[Fabian]

Binary package hint: nautilus

When trying to access files via sftp with Nautilus I get the following error message:

»sftp://192.168.128.1/« konnte nicht angezeigt werden.
Fehler: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)
Bitte wählen Sie einen anderen Betrachter und versuchen Sie es erneut.

Accessing the files via sftp works from a different computer in the same network.

ProblemType: Bug
Architecture: i386
Date: Thu Aug 6 10:59:29 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.27.4-0ubuntu3
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SourcePackage: nautilus
Uname: Linux 2.6.31-5-generic i686

[Sebastien Bacher (seb128)]

thank you for your bug report, did you connect to your server before? is gvfs-sftp crashing?

[Fabian (fabian-h)]

I connected from a different computer to this server (and I also tried a different server, getting the same error message). Connecting to the same server with smb does work.

There is no crash, just this error message appears directly after I press Enter.

I just now tried connecting via ssh on a terminal to this server and it worked. I added the server to the known_hosts and I could connect. After that it also worked in Nautilus. If I delete the "known_hosts" in ".ssh" I get the error message again.

So it seems the problem is ssh asking, if the server should be added to known_hosts.

[Sebastien Bacher (seb128)]

the issue is bug #403223

[Fabian (fabian-h)]

I'm not sure if this is a duplicate of #403223. There is no crash here, just the error message.

I also tried just calling "gvfs-mount sftp://server" and I just get the same error message, but no crash:
Error mounting location: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)

[Sebastien Bacher (seb128)]

you can try to browse a known location so gvfsd-sftp is running, using gdb on it and see if it's crashing when you connect to the one which timeout

[Sebastien Bacher (seb128)]

the issue is most likely the same one you can also wait for the other bug to be fixed and see how it goes for you

[Sebastien Bacher (seb128)]

(better to comment on the other bug too)