If what you are experiencing is similar to this post it would appear that this has been identified as an upstream issue which @laurent has been trying to sort out with the package maintainer.