According to the changelogs this bug has been fixed in 3.2.0-2, which has unfortunately not entered testing yet Please close the ticket accordingly, as I suspect this will prevent a newer (fixed) version from being migrated to testing.