tags 527942 + fixed-upstream I contacted upstream and provided an updated patch, which was accepted and released in 0.1.18d Upgrading the package to the latest upstream version should be sufficient to close this bug.