The bug has been fixed upstream in (not yet released) version 3.34,
feel free to close the report.

Reply via email to