hey,

i can confirm that latest version (0.24.2-5) works fine without those errors. so #513 can probably be closed. maybe #515 also, that seems a duplicate..

cheers,
d.