According to the upstream report, this was supposedly fixed in 2.0.10.
I haven't tested that specific version, but 2.0.21-2~bpo70+3 from wheezy-backports does NOT contain this bug anymore, while I did have the same problem as the bug submitter when using 2.0.6-4+deb7u2 from wheezy. Regards, Christian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
