sipatha, I cannot reproduce this on a current hardy install (and oalso on gutsy).
If I connect to a server where I don't have setup public key authentication (and so get asked for a password), it almost immediately beeps and does not complete anything. If I connect to a nonexistent IP, it will timeout after 10 seconds, beep and not complete anything. In neither case I get an error message. So I'm not sure what's going wrong in your case... I just tried with a virtualbox install of gutsy and get the same behavior as in hardy. What's happening if you do: ssh user@<my_ip_address> Does it time out? How much time passes until it does? BTW: I don't like the idea of completing local paths in this case. It does not make any sense and is very confusing. It's better to not complete anything. But of course the timeout should come sooner in your case and without the error message... -- Terminal hangs when using SCP https://bugs.launchpad.net/bugs/220127 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
