Comment 7 for bug 851834

I think it would be good to get a network-level capture of the problem. Even though it's encrypted, that may go down at least to the TLS/SSL packetization layer enough to let us understand more what's going on.

To do this:

 * install tcpdump
 * sudo tcpdump -i eth0 -p ip net 91.189.89.0/24 and tcp port 443 -w /tmp/lp.dump
 * while that's running, in another window, run the problematic bzr command
 * after bzr fails, press ctrl-C on tcpdump
 * attach /tmp/lp.dump to this bug

If you're behind an https proxy, please let us know, because firstly that may be the cause of the problem and secondly you will need to adjust the tcpdump expression.