Ok, thank you for the precision.
This is not completly fixed by revision rev#78602.