shazbot, 4 months ago

Getting back to you, this issue has been extensively described and reported by another user on this ticket. The bug is now fixed and will make its way into the next release (3.2.0).