deja-dup fails when launched automatically

[Wolf Rogner]

In #1727653 an error was reported that stated that backup using duplicity failed.

However, the error only manifests in duplicity but is triggered by the calling Deja-Dup.

Launching Deja-Dup automatically will ALWAYS lead to the error.

Launching Deja-Dup from the console/bash will NEVER lead to the error.

Any attempts to set number of open file limits do not remedy the issue.

Please refer to #1727653 and associated errors as all analysis have gone into duplicity so far.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: deja-dup 36.3-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 12 18:55:12 2018
InstallationDate: Installed on 2017-10-20 (84 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

[Vej (vej)]

Hello Wolf,

thanks for taking the time to improve Déjà Dup and Duplicity.

To mark another package as affected by a bug you should simply use the link "Also affects project" on the original bug. Opening a bug to get someone else to do this is not the preferred way here.

This is not a valid bug and will therefore be marked as invalid.

Best

Vej

[Wolf Rogner (war-rsb)]

Hello Vej,

to hear that an issue is not an issue is quite irritating.