AFAICT, this bug is fixed since version 3.2.0-1 although not mentioned in the
changelog.

Regards,
Jörg-Volker.

Reply via email to