[Bug 1730451] Re: MemoryError while verifying backup

- Please post the duplicity command line. - Please do an 'ls -l' or equivalent of the backup target directory and add as an attachment to this bug report. (see green + at bottom of display). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1730451] Re: MemoryError while verifying backup

Is this the backup causing the error reported? If not, please run against that one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730451 Title: MemoryError while verifying backup To manage

[Bug 1730451] Re: MemoryError while verifying backup

Also, would you please provide the duplicity command line for the incremental? ** Changed in: duplicity Milestone: None => 0.8.00 ** Changed in: duplicity Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman) ** Changed in: duplicity Importance: Undecided => High *

[Bug 1730451] Re: MemoryError while verifying backup

OK, sounds like the distro is keeping up. I like that. One way to find out how many incrementals you have is "--collection- status", like so: $ duplicity --collection-status and then counting the number of incrementals for the current backup. As a rule of thumb, you should have fewer that 30

Re: [Bug 1730451] Re: MemoryError while verifying backup

@Olivier, - When you upgraded to 0.7.15, did you remove the distro's version? - How much memory do you have? Is it the same as previous? - How long of an incremental change list do you have? - Have you tried making a full backup? On Wed, Jan 17, 2018 at 2:22 PM, Olivier Crête

[Bug 1743247] Re: B2 Python APIs are missing

0.7.15 included a rewrite of the b2 backend to be much faster. The rewrite uses the official b2 API, not web access, thus the need for the package. If you issue the commands below, you should see similar results: ken@dione:~$ pip --version pip 9.0.1 from /usr/local/lib/python2.7/site-packages

[Bug 1722454] Re: Duplicity fails with MemoryError

*** 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 Ubuntu

[Bug 1743247] Re: B2 Python APIs are missing

0.8.0, but I hope the comments above help for now. ** Changed in: duplicity Importance: Undecided => Medium ** Changed in: duplicity Status: New => In Progress ** Changed in: duplicity Milestone: None => 0.8.00 ** Changed in: duplicity Assignee: (unassigned) => Ken

[Bug 1743247] Re: B2 Python APIs are missing

** Also affects: duplicity 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/1743247 Title: B2 Python APIs are missing To manage notifications about this

[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

** 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

[Bug 1731631] Re: KeyError: 56

** 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/1731631 Title: KeyError: 56 To manage notifications about this bug go to:

[Bug 1742294] Re: duplicity crashes with memory error

Please upgrade to the current version of duplicity, 0.7.15. This will assure that any bugs fixed since 0.7.06 are available and will fix your issue. There are three options: * Release tarball Install - https://launchpad.net/duplicity/+download * Daily duplicity builds -

[Bug 498933] Re: Crash when restoring data KeyError

Please upgrade to the 0.7.15 version of duplicity. This will assure that any bugs fixed since the 0.7.12 release are available and may fix your issue. There are three options: * Release tarball Install - https://launchpad.net/duplicity/+download * Daily duplicity builds -

Re: [Bug 1733326] Re: Backup failed with an unknown error. .... MemoryError

Nope, not yet. We have one contributor working on it, but his time is limited. On Wed, Nov 29, 2017 at 3:35 AM, Matthias Klose wrote: > > Ummm, long discussion short, Ubuntu and I don't agree > > on releases. They release every six months and the > > version they pick up is

[Bug 1733326] Re: Backup failed with an unknown error. .... MemoryError

Ummm, long discussion short, Ubuntu and I don't agree on releases. They release every six months and the version they pick up is always at least one behind mine. I release when things are ready, and up the bug version with each release. For some reason they refuse to work that way, so to get

[Bug 1733326] Re: Backup failed with an unknown error. .... MemoryError

Please upgrade to the current version of duplicity. This will assure that any bugs fixed since your release are available and will fix your issue. There are three options: * Release tarball Install - https://launchpad.net/duplicity/+download * Daily duplicity builds -

Re: [Bug 1729695] Re: ASCII decode error, but not due to filenames in backup target

Take a look at the message in duplicity-team called "Help with unicode branch (for Python3 support)". It turns out that uexc() is using ufn() which is calling sys.getfilesystemencoding(). We may have a fix, not implemented yet, for sys.getfilesystemencoding() returning 'ascii' or None when

[Bug 1731631] Re: KeyError: 56

** Also affects: duplicity Importance: Undecided Status: New ** Changed in: duplicity Status: New => In Progress ** Changed in: duplicity Importance: Undecided => Medium ** Changed in: duplicity Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman) *

[Bug 1727653] Re: error: can't start new thread

This will work when duplicity is run from DejaDup, not when it is run from the console or from cron. The system wide solution above will work for all situations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1730451] Re: MemoryError while verifying backup

*** 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 Ubuntu Bugs, which

Re: [Bug 1727653] Re: error: can't start new thread

ulimit is settable system wide, so, at the end of /etc/security/limits.conf add the lines: *softnfile 16384 *hardnfile 32768 then reboot the system. That will set system wide limits for all tasks. On Sun, Nov 5, 2017 at 4:29 AM, Wolf Rogner

Re: [Bug 1727653] Re: error: can't start new thread

Do you have a passphrase on the backup? I don't see any key use, and it looks like gpg-agent is turned off. On the gpg processes, could you run an strace and see what fd it is hanging on? "strace -p " should do it. You can get a debug trace by doing: DEJA_DUP_DEBUG=1 deja-dup --backup from

[Bug 1727653] Re: error: can't start new thread

0.7.15 is coming out soon, .16 down the road. .15 preview is in the daily builds. Were you able to increase ulimit -n? What setting? I'm going to need a debug log. Could you run this with -v9 and supply two files, 1) the first 200 lines of the log 2) the last 200 lines of the log Please

[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

** 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

Re: [Bug 1727653] Re: error: can't start new thread

"Artful Aardvark" - Release amd64 > (20171018) > SourcePackage: duplicity > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/ > 1727653/+subscriptio

[Bug 1727653] Re: error: can't start new thread

If you could, please test the latest bzr trunk version. I just fixed a major bug that was chewing up a lot of memory. That may help with this problem if the fix above does not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1728720] Re: error: can't start new thread

*** This bug is a duplicate of bug 1727653 *** https://bugs.launchpad.net/bugs/1727653 ** This bug has been marked a duplicate of bug 1727653 error: can't start new thread -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1727653] Re: error: can't start new thread

** Summary changed: - duplicity fails with unknown error + error: can't start new thread -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727653 Title: error: can't start new thread To manage

[Bug 1727653] Re: duplicity fails with unknown error

You probably want to increase that. It's an extremely low limit. Search for "ubuntu increase max files limit" and you will find answers. Don't be miserly, set it at 32K or 64K. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1727653] Re: duplicity fails with unknown error

How many open files allowed ("ulimit -n")? Other than memory, "too many open files" has been the culprit that keeps fork from working. On Sat, Oct 28, 2017 at 1:10 PM, Wolf Rogner wrote: > Please read my comment again: > > Only when autostarted the error occurs. When launched

[Bug 1727653] Re: duplicity fails with unknown error

ess ** Changed in: duplicity (Ubuntu) Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727653 Title: duplicity fails with unknown error To

Re: [Bug 1278529] Re: Using S3, "BackendException: No connection to backend"

Please upgrade to the current version of duplicity. This will assure that any bugs fixed since your release are available and may fix your issue. There are three options: - Release tarball Install - https://launchpad.net/duplicity/+download - Daily duplicity builds -

Re: [Bug 1722454] Re: Duplicity fails with MemoryError

*** 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

[Bug 1727995] Re: Backup Failed with Unknown Error (MemoryError)

*** 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 Ubuntu Bugs, which

[Bug 1722454] Re: Duplicity fails with MemoryError

*** 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 Ubuntu Bugs, which

[Bug 1727653] Re: duplicity fails with unknown error

*** 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 Ubuntu Bugs, which

[Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)

** Changed in: duplicity Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538333 Title: AssertionError in manifest.py: assert filecount ==

[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

** 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 Ub

[Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)

* Fixed bug #1538333 Assertion error in manifest.py: assert filecount == ... - Made sure to never pass .part files as true manifest files - Changed assert to log.Error to warn about truncated/corrupt filelist - Added unit test to make sure detection works - Note: while this condition is

[Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)

in: duplicity Status: In Progress => Fix Committed ** Changed in: duplicity Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538333

[Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)

** Changed in: duplicity Status: Incomplete => In Progress ** Changed in: duplicity Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchp

[Bug 1166019] Re: duplicity crashed with SIGSEGV in g_file_copy()

Please upgrade to the current version of duplicity. This will assure that any bugs fixed since your release are available and should fix this issue. There are three options: * Release tarball Install - https://launchpad.net/duplicity/+download * Daily duplicity builds -

[Bug 1710309] Re: Backup does not recognize gpg 2 option and fails

This is not something duplicity controls. If gpg is saying that it does not recognize the trust model supplied in gpg.conf, then the bug could be that the version of gpg on the system is too old for this trust model. It is not in duplicity since duplicity has no reason to read gpg.conf. Perhaps

[Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)

I have been unable to reproduce this in testing. If you encounter this error, please provide the following: 1) full command line 2) full unencrypted manifest file (attached as a file) 3) detailed (ls -l style) listing of the remote system (attached as a file) 4) as much of the logging as

[Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)

I have been unable to reproduce this in testing. If you encounter this error, please provide the following: 1) full command line 2) full unencrypted manifest file (attached as a file) 3) detailed (ls -l style) listing of the remote system (attached as a file) 4) as much of the logging as

[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

** 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

[Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)

** Changed in: duplicity Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538333 Title: AssertionError in manifest.py: assert filecount == len(self.files_changed) To

[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

** 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

[Bug 1689951] Re: System locks up unrecoverably after CPU soft lockup

** No longer affects: duplicity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1689951 Title: System locks up unrecoverably after CPU soft lockup To manage notifications about this bug go to:

[Bug 989750] Re: repeatedly asks for encryption password when backing up, even though "remember password" is ticked

This has long been fixed, so closing it now. Please upgrade to the current version of duplicity. This will assure that any bugs fixed since your release are available and my fix your issue. There are three options: * Release tarball Install - https://launchpad.net/duplicity/+download * Daily

[Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)

This bug was fixed in 0.7.07.1. I cannot reproduce. ** Changed in: duplicity Status: In Progress => Won't Fix ** Changed in: duplicity Status: Won't Fix => New ** Changed in: duplicity Milestone: 0.7.13 => None -- You received this bug notification because you are a member

[Bug 1538333] Re: AssertionError in manifest.py: assert filecount == len(self.files_changed)

Reopening ** Changed in: duplicity Status: Fix Released => In Progress ** Changed in: duplicity Milestone: 0.7.07 => 0.7.13 ** Changed in: duplicity Assignee: (unassigned) => Michael Terry (mterry) -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

** 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

Re: [Bug 1669616] Re: please consider updating to >=0.7.08

So, if we could extract just the bug fixes, how would you want them? Patch? Merge? ...Ken Duplicity Maintainer On Thu, Mar 2, 2017 at 6:42 PM, Vej wrote: > I would like to see 0.7.08 or higher for zesty. But zesty is feature > freeze, which forbids the introduction

[Bug 1519103] Re: Shell Code Injection in hsi backend

This bug was fixed in duplicity 0.7.07. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519103 Title: Shell Code Injection in hsi backend To manage notifications about this bug go to:

[Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

** 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

Re: [Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

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.

[Bug 1660345] Re: 'Is plugged to a power source' checkbox missing

This is not a duplicity error. Please redirect to correct project. ** Changed in: duplicity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660345 Title: 'Is

[Bug 1177381] Re: Duplicity can't find its own tempdir

) => Kenneth Loafman (kenneth-loafman) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177381 Title: Duplicity can't find its own tempdir To manage notifications about this bug go to: https://bug

Re: [Bug 1177381] Re: Duplicity can't find its own tempdir

@Michael, I'm looking as well. My gut says that something got threaded and we're not joining at the end of the run, but I cannot find any indication of that at all. On Wed, Dec 14, 2016 at 5:48 PM, Karl <1177...@bugs.launchpad.net> wrote: > I'm using a laptop with my power settings set to "Do

Re: [Bug 1642437] [NEW] duplicity crashes when network connection is lost

What is the command line you are using? Some backends are better than others at recovery. On Wed, Nov 16, 2016 at 6:37 PM, Thrilway <1642...@bugs.launchpad.net> wrote: > Public bug reported: > > Python traceback attached in a separate file > > ProblemType: Bug > DistroRelease: Ubuntu 16.10 >

[Bug 1640558] Re: 16.10 Backup Failure.

What version of duplicity? What command line? ** Changed in: duplicity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640558 Title: 16.10 Backup

[Bug 1612554] Re: duplicity backup fails with OverflowError: size does not fit in an int

Marking invalid because duplicity does not support sparse files, yet. ** Changed in: duplicity Status: In Progress => Invalid ** Changed in: duplicity Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned) -- You received this bug notification because you are a

Re: [Bug 1612554] Re: duplicity backup fails with OverflowError: size does not fit in an int

Yep, exclude that and it should work. On Tue, Aug 23, 2016 at 6:33 AM, Peter Van Rompaey wrote: > Re-ran the incremental backup, but it fails with the same error while > adding /var/log/lastlog, which is a sparse file with a reported size of > 36Gb, but actually only 56k on

[Bug 1612554] Re: duplicity backup fails with OverflowError: size does not fit in an int

It's possible that the last incremental was corrupted. Try this: - duplicity cleanup --force - remove the last incremental backup, easiest is by date in the filename - duplicity inc -v9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1612554] Re: duplicity backup fails with OverflowError: size does not fit in an int

** Changed in: duplicity Status: Invalid => In Progress ** Changed in: duplicity Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman) ** Changed in: duplicity Importance: Undecided => Medium -- You received this bug notification because you are a member of Ub

Re: [Bug 1612554] Re: duplicity backup fails with OverflowError: size does not fit in an int

do this: $ apt-cache show librsync1 That will display the version. On Mon, Aug 22, 2016 at 3:16 AM, Peter Van Rompaey wrote: > I didn't install any specific version, since it was included in the > duplicity tarball: > > $ tar tf duplicity-0.7.09.tar.gz | grep -i rsync >

Re: [Bug 1612554] Re: duplicity backup fails with OverflowError: size does not fit in an int

What version of librsync? On Fri, Aug 19, 2016 at 3:52 AM, Peter Van Rompaey wrote: > Cried victory too soon, I'm afraid. > > I have: > - compiled python 2.7.12 with the zlib patch > - created a virtualenv with that version > - installed duplicity in the virtualenv, along

[Bug 1612554] Re: duplicity backup fails with OverflowError: size does not fit in an int

Marking as invalid since this problem is not with duplicity itself. ** Changed in: duplicity Importance: Medium => Undecided ** Changed in: duplicity Milestone: 0.7.10 => None ** Changed in: duplicity Status: New => Invalid -- You received this bug notification because you are a

[Bug 1612554] Re: duplicity backup fails with OverflowError: size does not fit in an int

** Changed in: duplicity (Ubuntu) Status: Invalid => New ** Also affects: duplicity Importance: Undecided Status: New ** Changed in: duplicity Importance: Undecided => Medium ** Changed in: duplicity Milestone: None => 0.7.10 -- You received this bug notification

[Bug 1612554] Re: duplicity backup fails with OverflowError: size does not fit in an int

This has been fixed for a couple of years. Please upgrade to a newer version using the duplicity PPA or through the tarball in the download area. The 0.6 series has been deprecated in the upstream. The 0.7 series is current. Please be aware that you will need to 'apt-get remove duplicity'

[Bug 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

** Changed in: duplicity (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1217959 Title: 'metadata' file not found when creating backup ("Could not

Re: [Bug 1356548] Re: Duplicity restore fails with UTF-8 chars in --file-to-restore

This bug is fixed in the latest versions, the 0.7 series at duplicity . Please upgrade. If you are on 0.6 series, please do not report new bugs about this, they won't be fixed. To upgrade to the newest, 1. Remove the old version installed from the

Re: [Bug 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"

Go here and add the repository to your list. apt-get update / upgrade will bring in the latest version which is a lot newer than the one you have. 0.6.21 is at least 3 years old and has been superseded. On Wed, Jun 1, 2016 at 3:46 AM,

Re: [Bug 1576514] [NEW] After upgrade to Xenial Duplicity crashes "No module named lockfile"

What version of duplicity? On Fri, Apr 29, 2016 at 12:22 AM, Gaussian <1576...@bugs.launchpad.net> wrote: > Public bug reported: > > After upgrade to Xenial Duplicity crashes with: > > > Traceback (most recent call last): > File "/usr/bin/duplicity",

[Bug 1434702] Re: incorrect response BackendException while downloading signatures file

Go to https://launchpad.net/~duplicity-team/+archive/ubuntu/ppa to and add the repository to your system. Upgrade from there to get the latest stable release. Go to https://launchpad.net/~duplicity- team/+archive/ubuntu/daily for daily builds. The Ubuntu repos are ancient at the best of times.

[Bug 1434702] Re: incorrect response BackendException while downloading signatures file

This was fixed in version 0.7.03 in the trunk on 05/11/2015. We are up to 07.07.1 as of 04/19/2016. You might want to upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1434702 Title:

Re: [Bug 1318833] Re: duplicity backup fails in 14.04

OK, try that first. It can get confused if two versions are present. On Sat, Apr 2, 2016 at 10:37 AM, François Pernoud < 1318...@bugs.launchpad.net> wrote: > The command line is : > > duplicity --include-filelist duplicity.list -vi $HOME > file::///media/francois/hubic/default/sauvegardes > >

Re: [Bug 1318833] Re: duplicity backup fails in 14.04

What command line? Did you uninstall the repo version of duplicity before installing from source? On Fri, Apr 1, 2016 at 2:43 AM, François Pernoud <1318...@bugs.launchpad.net > wrote: > Same problem here with duplicity 0.7.06, run from terminal on Ubuntu > 15.10. > > Not every run fails, so I

Re: [Bug 1563738] [NEW] duplicity throws traceback on backuping to sftp

It looks like you still have 0.6.23 installed. You will need to apt-get remove the distro version then reinstall the version from source. On Wed, Mar 30, 2016 at 4:00 AM, Saad Ismail wrote: > Public bug reported: > > Hello, > > I just installed duplicity-0.7.06 from source

Re: [Bug 1318833] Re: duplicity backup fails in 14.04

Go to https://launchpad.net/duplicity/+download and download the latest duplicity. 0.6.13 is old and on a deprecated branch. Before you run setup.py, run "sudo apt-get purge duplicity" to get rid of the older version. Then run "tar xf duplicity-0.7.06.tar.gz; cd duplicity-0.7.06; sudo python

Re: [Bug 1245805] Re: Crash with stacktrace, error code 30 in validate_encryption_settings

This error is due to missing volumes. Try doing a 'duplicity cleanup --force ', then run the backup again. On Sun, Jan 3, 2016 at 3:06 AM, macho <1245...@bugs.launchpad.net> wrote: > I'm still getting this crash on Ubuntu 15.10 with duplicity 0.7.02. > > My initial full backup seemed to be

[Bug 1434702] Re: incorrect response BackendException while downloading signatures file

** Also affects: 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/1434702 Title: incorrect response BackendException while downloading signatures

[Bug 1223055] Re: System Hangs With Kernel Migration Processes Consuming 100% CPU

I do not believe that this bug is isolatable to zorg. I have seen this bug at least weekly and I'm keeping my 12.04 system up-to-date. I can sometimes get around the problem by killing off tasks, starting with Chrome and Eclipse, that use a lot of threads, but that takes a lot of patience. I'd

[Bug 1454333] Re: Traceback from get_backup_chains

** Summary changed: - Traceback (most recent call last): File /usr/bin/duplicity, line 1500, in module with_tempdir(main) File /usr/bin/duplicity, line 1494, in with_tempdir fn() File /usr/bin/duplicity, line 1343, in main do_backup(action) File /usr/bin/duplicity, line

[Bug 1166019] Re: duplicity crashed with SIGSEGV in g_file_copy()

Need the complete output from the -v9 log. ** Also affects: duplicity Importance: Undecided Status: New ** Changed in: duplicity Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1223055] Re: System Hangs With Kernel Migration Processes Consuming 100% CPU

** Also affects: linux-kernel-64 (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/1223055 Title: System Hangs With Kernel Migration Processes

[Bug 1223055] Re: System Hangs With Kernel Migration Processes Consuming 100% CPU

root@stealth:~# uname -a Linux stealth 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux The bug appears to be related directly to the number of processes. I have 4 processors and 16GB of memory and normally only hit this problem when I have greater

[Bug 1278529] Re: Using S3, BackendException: No connection to backend

** Changed in: duplicity Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-boto in Ubuntu. https://bugs.launchpad.net/bugs/1278529 Title: Using S3, BackendException: No connection to

[Bug 1278529] Re: Using S3, BackendException: No connection to backend

** Changed in: duplicity Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278529 Title: Using S3, BackendException: No connection to backend To manage

[Bug 1278529] Re: Using S3, BackendException: No connection to backend

** Changed in: duplicity Importance: Undecided = Medium ** Changed in: duplicity Status: Confirmed = Fix Committed ** Changed in: duplicity Milestone: None = 0.7.01 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to

[Bug 1278529] Re: Using S3, BackendException: No connection to backend

** Changed in: duplicity Importance: Undecided = Medium ** Changed in: duplicity Status: Confirmed = Fix Committed ** Changed in: duplicity Milestone: None = 0.7.01 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 510625] Re: Bad parsing of GnuPG output, expecting english output, which doesn't work if locales different than english.

** Changed in: duplicity 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/510625 Title: Bad parsing of GnuPG output, expecting english output, which doesn't work if

[Bug 629357] Re: [Feature Request] support xz for compressing volumes

** Changed in: duplicity (Ubuntu) Status: Confirmed = Opinion ** Changed in: duplicity Status: New = Opinion ** Changed in: duplicity Importance: Wishlist = Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1388633] Re: crashes with code 30 (OverflowError) at start

This bug was fixed in 0.6.25. Please update. On Sat, Nov 22, 2014 at 4:05 AM, Kai Stian Olstad 1388...@bugs.launchpad.net wrote: You are backing up from root /, when you do that you should at least exclude /dev /proc /sys Other good excludes are: /media /root/.cache/duplicity /tmp

[Bug 1388633] Re: crashes with code 30 (OverflowError) at start

*** This bug is a duplicate of bug 1327550 *** https://bugs.launchpad.net/bugs/1327550 ** This bug has been marked a duplicate of bug 1327550 OverflowError: signed integer is greater than maximum -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1294201] Re: Uploading of backup to Ubuntu One fails with 400 Bad Request

** Changed in: duplicity Status: New = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294201 Title: Uploading of backup to Ubuntu One fails with 400 Bad Request To manage

[Bug 1313966] Re: duplicity cannot back up files from Russian file directory

** Changed in: duplicity Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313966 Title: duplicity cannot back up files from Russian file directory To

[Bug 1311176] Re: crash deja-dup backup ascii' codec can't decode byte 0xc3

** Changed in: duplicity Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311176 Title: crash deja-dup backup ascii' codec can't decode byte 0xc3 To

[Bug 1286845] Re: UnicodeEncode error from Backup Statistics

** Changed in: duplicity Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286845 Title: UnicodeEncode error from Backup Statistics To manage notifications

<    1   2   3   4   5   6   >