There's a strong likelyhood that this is a dup of bug 659590.... in which case I've already had a fix landed on lp:bzr/2.2 :-)
There's a strong likelyhood that this is a dup of bug 659590.... in which case I've already had a fix landed on lp:bzr/2.2 :-)