Traceback (most recent call last): File "/usr/bin/duplicity", line 1359, in <module>

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1359, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1342, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1276, in main
    restore(col_stats)
  File "/usr/bin/duplicity", line 591, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in Write_ROPaths
    ITR( ropath.index, ropath )
  File "/usr/lib/python2.7/dist-packages/duplicity/lazy.py", line 335, in __call__
    last_branch.fast_process, args)
  File "/usr/lib/python2.7/dist-packages/duplicity/robust.py", line 37, in check_common_error
    return function(*args)
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 576, in fast_process
    ropath.copy( self.base_path.new_index( index ) )
  File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 425, in copy
    other.writefileobj(self.open("rb"))
  File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 605, in writefileobj
    if fin.close() or fout.close():
IOError: [Errno 7] Argument list too long

I suggest you run:

ubuntu-bug deja-dup

To report the bug

[I see that you have already reported this bug, so the advice below is not relevant--any missing information in the bug report can be requested by triagers/developers and provided. Nonetheless, I am posting this anyway, with the hope that it will help others in similar situations reporting bugs.]

Before reporting this bug, please make sure to read https://help.ubuntu.com/community/ReportingBugs carefully.

Rather than by running "ubuntu-bug deja-dup", is preferable to report this bug by enabling Apport crash reporting (https://wiki.ubuntu.com/Apport#How_to_enable_apport) and triggering the crash, as that will automatically attach critically important information including (but not just) the complete traceback. If for any reason you are unwilling to do that, then you can still report the bug with "ubuntu-bug deja-dup" (just make sure to include the traceback you included here, and be especially prepared to be asked by triagers or developers for additional information). However, if you are willing to report the bug in that way but have trouble doing so, please feel free to ask for further help here in this question.

However you report this bug, please make sure to include a complete description of the actions you take to produce it (which you did not include here).

Your bug report should be complete and self-contained, such that it is not necessary for an Ubuntu developer to refer to this question in order to fully understand and appreciate the problem. However, you should nonetheless link the bug and this question together, using "Link existing bug" on this question page.