This issue was fixed in the latest upstream version, v5.1.6. Please update when 
you can.

Reply via email to