This bug was fixed in version 1:1.0.0-6.

Cheers,

Timo

Reply via email to