Recieved word from the author that this isue wil be fixed in the next upstream 
release 1.3.1

Reply via email to