I believe this was fixed upstream in 2.10.0 (commits f62c2b8 and 0b22580).

--
Vassili Tchersky

Reply via email to