Patch accepted by upstream (in git). So with packaging upcoming version 0.5.4.3 
this bug may be closed.

Reply via email to