Hi,
Thank you for reporting this issue. It has been completely fixed in version 3.3, now available here and through automatic updates.
Nicolas