I tried running
DEJA_DUP_DEBUG=1 deja-dup --backup | tee ~/deja-dup-backup-debug.log
hoping the debug log would show which file would contain the 0xe2 byte in its filename so that I could delete or at least exclude it.
But although the debug.log is rather verbose it wouldn't tell which file made it fail.
Is there a way to make deja-dup reveal what file brings it down?
I tried running dup-backup- debug.log
DEJA_DUP_DEBUG=1 deja-dup --backup | tee ~/deja-
hoping the debug log would show which file would contain the 0xe2 byte in its filename so that I could delete or at least exclude it.
But although the debug.log is rather verbose it wouldn't tell which file made it fail.
Is there a way to make deja-dup reveal what file brings it down?