This bug appears to have been fixed in version 2.2.


Reply via email to