Comment 2 for bug 931206

It seems most likely that there was an update that broke some things for you. The solution is to run arbtt-recover, then take the capture.log and rename it to something else (that is, back it up instead of deleting it), then rename capture.log.recovered to capture.log.

@Joachim: The similar error I encountered was "arbtt-stats: Prelude.chr: bad argument: 1728640". When I used arbtt-recover, it gave me a lot of outputs like this: "Failed to read value at position 6811645:
   Unsupported TimeLogEntry version tag 112"

Does this help? Unfortunately, I don't remember if there was a recent upgrade.... But on the bright side, arbtt-recover saved all the data for me perfectly.