I finally managed to reproduce the problem and I fixed it in v1.5.2. This
bug report should be closed once the package gets in Debian and the fix is
confirmed.

Thanks a lot for the report. This bug is quite important.

Reply via email to