If this bug has been reported, I failed to find it on Launchpad. There have been numerous "TooManyConcurrentRequests" bugs filed, but most/all of them seem to be related to legitimate attempts to open an ssh connection. I have found a case in which there seems to be no legitimate reason to involve ssh. Before posting this to the list, I have taken a step back from the edge and am using only the stable ppa (<a href="http://ppa.launchpad.net/bzr/ppa/ubuntu">http://ppa.launchpad.net/bzr/ppa/ubuntu</a>) to get my bzr components for Linux. As a result, I'm running bzr 2.2.0 (via 2.2.0-1~bazaar4~lucid1) but still on qbzr 0.19.0 (via 0.19-1~bazaar1~lucid1). I do not know if what I am about to describe is already resolved in releases not yet in the stable ppa. I also have bzr (also 2.2) installed on a remote machine we'll call <a href="http://server.net">server.net</a>. On that machine, a user 'user' owns some branches and also has a copy of my ssh public key. So on my local working machine I do something like <div style="margin-left: 40px;">'bzr checkout bzr+ssh//<a href="http://user@server.net/home/user/test/trunk">user@server.net/home/user/test/trunk</a> <localpath>/test' </div> to get a checkout. That works fine, of course. Now, if on the local machine I open this checkout with Bazaar Explorer, most things work fine. But if I select Settings > Configuration > User Configuration, Bazaar Explorer crashes when the dialog is closed with <div style="margin-left: 40px;">bzr: ERROR: bzrlib.errors.TooManyConcurrentRequests: The medium 'SmartSSHClientMedium(bzr+ssh://<a href="http://user@server.net/">user@server.net/</a>)' has reached its concurrent request limit. Be sure to finish_writing and finish_reading on the currently open request. </div> If I open the same settings dialog either from the Welcome page or from a page associated with a real branch (not a checkout) then everything is ok. So it *appears* that either qconfig or explorer is triggering an illegitimate ssh connection request when the active GUI page is a checkout via bzr+ssh. I am attaching a traceback which pops in a dialog but does *not* get written to .bzr.log. Thoughts? ~M