First, an apology. The machine details were from the wrong machine :-) [I was sshed into the target machine, but managed to run reportbug from the host machine rather than on the target machine.]
However, I don't think that is important. I have just seen and contributed to a thread on the upstream mailing list where I see that bug 626417 is almost certainly the same problem. Turning off -1 to stop most multithreading cures the problem here, so I suspect a race condition exposed in 6.3.3-3 which maybe was hidden in earlier versions. ael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
