@Jason: That recover is spilling out lots of text is normal, as it is
quite brutally trying to skip some amount of data and continue reading.
The cause could also be a broken read, e.g. when the user logs out
precicely while arbtt-capture is writing data, or maybe two arbtt-
capture instances ran
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: arbtt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931206
Title:
Crash
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
Hi. What is your version of arbtt? Was there an upgrade recently?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931206
Title:
Crash when running arbtt-dump or arbtt-stats
To manage notifications ab
