Results 11 comments of Leonardo Robol

This should have been fixed in the latest release. May you check if the problem still persists with 3.2.2?