My workaround for this problem:
i went to the backupserver where our remote backups are located
ls -latr *.sigtar.gz
(pick the last one and gave it a "_" as prefix)
after that i could do a purge again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: duplicity
Status: Confirmed => Incomplete
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
** Changed in: duplicity
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Snarky and off topic, but true.
I've left this bug open intentionally since it happens on occasion. I
don't believe duplicity is at fault. Mostly these kind of errors happen
because of:
-- Ctrl-C happy users and Python's poor handling of signals.
-- Consumer grade electronics with: memory
Wow, this is so interesting. Almost 10 years old bug, official (!)
Ubuntu app for backup, and not fixed yet.
Guys, seriously. I highly recommend BordBackup. It is reliable, fast,
has an active development (!) and GUI frontend. And yes, it is working
on different OS'es.
--
You received this bug
This bug just happened on my father's PC and I can provide steps to
reproduce:
1. Attempt to back up more files than can be stored onto the backup device
2. Backup fails with "not enough space error"
3. Change the configuration in order to be able to backup
4. Manually start a backup
The backup
It has been a long while since this occurred, except when restoring from
an older backup. What produced the zeroes is beyond my guess. Very
weird.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have some further details about this bug! Not super positive, but
still.
First, I'm going to mark bug #676767 a duplicate of this. That's a
slightly older bug with the same symptom, and a workaround (of deleting
the cache) that doesn't seem to work in all cases. But ultimately, it's
And thus ..
RESTORE FAILED
Failed to read /tmp/duplicity-fuftb7sx-tempdir/mktemp-24n9b1zc-1: (, OSError('CRC check failed 0x8b680b5 != 0x6ee58156',), )
So Deja-Dup can neither create a back-up nor restore one
remind me ..
What is this programme supposed to do ?
--
You received this bug
Sooo...
I ran Deja Dup from a terminal
The only output was
"Gtk-Message: 16:48:40.229: Failed to load module "canberra-gtk-module"
Gtk-Message: 16:48:40.244: Failed to load module "canberra-gtk-module"
until (I'm thinking inevitably)
Failed to read
Failed to read /tmp/duplicity-7esacbqs-tempdir/mktemp-jfb5sld2-2:
(, OSError('CRC check failed 0x940ae478 !=
0xc3978beb',), )
I haven't a clue about how do run a back-up anymore.
I use Deja-Dup exclusively and don't have spare HDD around to try a different
software.
How long before there's some
** Changed in: duplicity
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage
After running the backup again, I'm now getting this error message:
"UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position
37: ordinal not in range(128)".
Unfortunately, I've encountered this several times in the past. Also, I
can no longer see the backup log in the deja-dup gui,
I'm also seeing this error pop up in the last few days, despite not
making any changes to the backup configuration (using deja-dup).
Thanks Kenneth for the suggestion above about running with the -v9
command.
Is there a way that I could see the exact duplicity backup command
that's triggered by
A couple of things to check:
- If you run with -v9 you will get a long and detailed log of the run.
The individual file that is causing the problem should be listed. Test
that file by unzipping and decoding. If it fails, you can delete the
incrementals containing it and all subsequent
Hi,
This bug is affecting me still.
$ duplicity --version
duplicity 0.7.17
$ apt-cache show duplicity
Package: duplicity
Architecture: amd64
Version: 0.7.17-0ubuntu1
Priority: optional
Section: utils
Origin: Ubuntu
In the past (129 days ago!) I tried to fix this but got nowhere.
Given that
** Changed in: duplicity
Milestone: 0.7.17 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about
** Changed in: duplicity
Milestone: 0.7.16 => 0.7.17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about
** Changed in: duplicity
Milestone: 0.7.15 => 0.7.16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about
** Changed in: duplicity
Status: Confirmed => In Progress
** Changed in: duplicity
Milestone: 0.7.14 => 0.7.15
** Changed in: duplicity
Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Package changed: deja-dup (Ubuntu) => duplicity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications
** No longer affects: deja-dup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about this bug go to:
** Changed in: duplicity
Milestone: 0.7.13.1 => 0.7.14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications
** Changed in: duplicity
Milestone: 0.7.13 => 0.7.14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about
** Changed in: duplicity
Milestone: 0.7.12 => 0.7.13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about
** Changed in: deja-dup (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about this bug go to:
** Changed in: duplicity
Importance: Undecided => High
** Changed in: duplicity
Milestone: None => 0.7.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with
Setting to "Confirmed", because this bug affects multiple users.
** Changed in: deja-dup
Status: New => Confirmed
** Changed in: duplicity
Status: New => Confirmed
** Changed in: deja-dup
Importance: Undecided => High
--
You received this bug notification because you are a
There is a disconnect between Ubuntu distribution and upstream distribution
(me). Ubuntu will not, repeat will not, allow changes that add
functionality, or upgrade the version number of a product in a
distribution. I can't live with that, so my distribution version changes
with every release.
No that it is not good. This is completely irresponsible and lame.
It is a shame, that so important software is a part of core Ubuntu
system. Canonical should reconsider using it. Because backup is critical
and if DejaDup is a part of a core system, people rely on it.
--
You received this bug
I think I've got the same problem.
DejaDup with Ubuntu 16.04 prints the same error message and even
duplicity can't do anything in the backup folder. ("remove-older-than"
fails with "(, IOError('CRC check failed
0xb1276c7b != 0x9b944aa5L',), )".)
If I delete or move duplicity-new-
I have the same error with DejaDup in Ubuntu 16.04.
I am trying to run a backup (not restore!), and got this error:
Ni mogoče brati /tmp/duplicity-gUZKem-tempdir/mktemp-jecFmU-5: (, IOError('CRC check failed 0x5528869f !=
0x2aeb4411L',), )
It is in slovenian, but it means:
Cannot read
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: deja-dup (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/875676
Title:
Hello everyone,
Is this bug solved??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To manage notifications about this bug go to:
Every time I start a backup I get the following error:
Failed to read
/home/user/.cache/deja-dup/tmp/duplicity-7EsAky-tempdir/mktemp-hqHmHI-63:
(type 'exceptions.IOError', IOError('CRC check failed 0x6ae5ab23 !=
0x78b803e5L',), traceback object at 0x7f4f3cfa06c8)
Deleting the cace dir does not
** Also affects: deja-dup (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
To
36 matches
Mail list logo
