This bug was fixed in version 2.4.0.

Reply via email to