Thanks for the report. This bug has been fixed yesterday, after I got notified here and by mail of the problem and a new release (containing, among others, this bug fix) will be made available in one week or two.