Bug #50136 came up with a patch, which actually seems to fix the issue. I'll talk to upstream to have a look into it and maybe release a new version.
Bug #50136 came up with a patch, which actually seems to fix the issue. I'll talk to upstream to have a look into it and maybe release a new version.