This issue is now fixed by revision rev#68299 .
Thank you for the report.