FYI, this is fixed if upgrading to upstream release 1.1.3.

Cheers,

Thomas Goirand (zigo)

Reply via email to