rdiff-backup crashed with IOError in log_to_term()

[Toon Verwaest]

Binary package hint: rdiff-backup

While this bug seems to be fixed if I read the backlog of bugs, I now constantly get this error at the end of a backup. I guess something went wrong at some point and from there on it just always crashes with this error.

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/rdiff-backup
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: rdiff-backup 1.2.7-1ubuntu2
ProcCmdline: /usr/bin/python /usr/bin/rdiff-backup --exclude-other-filesystems / /media/Backup/hostname-backup/root
ProcEnviron:
 SHELL=/bin/sh
 PATH=(custom, no user)
PythonArgs: ['/usr/bin/rdiff-backup', '--exclude-other-filesystems', '/', '/media/Backup/hostname-backup/root']
SourcePackage: rdiff-backup
Title: rdiff-backup crashed with IOError in log_to_term()
Uname: Linux 2.6.29 x86_64
UserGroups:

[Michael Ferenczi (m-ferenczi)]

using backintime GUI and external USB 2.0 hard disk to back up to.

[Andreas Olsson (andol)]

@Michael: What does that has to do with this bug report? To my knowledge backintime isn't even using rdiff-backup.

[Andreas Olsson (andol)]

@Toon Verwaest: Working my way through old rdiff-backup bug reports now. Sorry about noone getting back to your earlier.

Are you still using Ubuntu 9.04 and rdiff-backup 1.2.7-1ubuntu2? Is still a problem you still experience?

Is this problem limited to a particular backup set, or do you also experience if you try creating a new backup set?

On what kind of filesystem does the destination directory reside?

You mentioned seeing this bug being mentioned in a backlog of fixed bugs? If you still know where to find that report, would it be possible to point towards it?

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future.
To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".