A new version 3.2 has been uploaded to unstable.

Could you please assist the maintainer by checking if this bug can
still be reproduced with latest version?

Reply via email to