Hello,

This bug was fixed long ago, the current unstable version 10.0.0.1 no
longer has this issue.
What must happen for this to be closed ?

Thanks,
Aaron

Reply via email to