*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
Hi,
my report looks different but syslog says memory error and when I set up a new
S3 bucket
test works just fine with the same credentials so this must be duplicity
related.
Unfortunately I do not get
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
Hi,
my report looks different but syslog reports memory error and when I set up a
fresh S3 bucket
test works just fine with the same credentials so this must be duplicity
related.
- It does the same with
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
Please upgrade to the current version of duplicity, 0.7.16. This will assure
that any bugs fixed since your release are available and may fix your issue.
This applies especially to duplicity versions
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
Adding my own t/b. It is little different from other posts on this page.
Version info:
$ apt show duplicity
Package: duplicity
Version: 0.7.12-1ubuntu1
Error:
Traceback (most recent call last):
File
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
Is it really a duplicate? I have now upgraded to the supposed fix of
#1720159
$ apt show duplicity
Package: duplicity
Version: 0.7.16+bzr1347-0ubuntu1~ubuntu17.10.1
... but still get the same error as
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
This bug report is a duplicate of: Bug #1720159: Cannot allocate memory
with large manifest file since 0.7.03. It has been fixed.
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
The same for me, it's look like is so long a file index. And isn't
depend of real memory amount. I've 20Gb RAM and it should be enough for
any operation even operations.
Traceback (most recent call last):
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
I get the exact same error. Backup is started automatically every week
and is only configured from the Ubuntu control panel. This only occurred
after upgrading to Ubuntu 17.10.
I have an i7 processor with
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
I also get the exact same traceback
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1722454
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: duplicity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
Understand this is a dup ticket, but I do get the exact same traceback
as posted in this ticket.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
Memory errors hit when you run out of memory. Sometimes it's a different
spot in the code. This traceback was from manifest.py, so an easy call.
On Fri, Oct 27, 2017 at 2:18 AM, Juerg Haefliger
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
Hmm... Why do you think this is a duplicate of #1720159? My stack trace
looks different.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
*** This bug is a duplicate of bug 1720159 ***
https://bugs.launchpad.net/bugs/1720159
** This bug has been marked a duplicate of bug 1720159
Cannot allocate memory with large manifest file since 0.7.03
--
You received this bug notification because you are a member of Desktop
Packages,
** Also affects: duplicity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1722454
Title:
Duplicity fails with MemoryError
Status in
Happened again the day after cleaning the cache.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1722454
Title:
Duplicity fails with MemoryError
Status in duplicity package in
Workaround is to purge the cache ~/.cache/deja-dup.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1722454
Title:
Duplicity fails with MemoryError
Status in duplicity package in
17 matches
Mail list logo