Added a debian bug watch - I'm not absolutely sure this is the same problem. The stacktrace here is a different one (and a corrupt one, mind you).
Added a debian bug watch - I'm not absolutely sure this is the same problem. The stacktrace here is a different one (and a corrupt one, mind you).