Comment 9 for bug 288260

The best bzr can do is give a slightly clearer description of its error. bzr can't realistically do anything about the way OpenSSH reports this failure as "muxserver_listen bind(): No such file or directory".

There's already a bug for improving bzr's error message in this case (bug 238776). If that gets fixed in the way I've proposed in <https://bugs.edge.launchpad.net/bzr/+bug/238776/comments/2> then you will see something like this instead:

$ bzr branch lp:bzr-upload
muxserver_listen bind(): No such file or directory
bzr: ERROR: Failed to establish SSH connection to <email address hidden>

Possibly that last line could also say "(using /usr/bin/ssh)", if you think that would help?

I think it is worth filing a bug on OpenSSH. I'm sure its error message could be improved, and it's really the right place to do it — the tool establishing the SSH connection is the only one with enough information to explain why establishing the connection failed.