Comment 6 for bug 394629

Cristian KLEIN wrote:
> Kenneth Loafman a écrit :
>> Cristian KLEIN wrote:
>>> Kenneth Loafman a écrit :
>>>> Is there any way to reproduce this? Does it happen all the time, or
>>>> just sometimes?
>>>>
>>>> I'm having a hard time replicating the problem.
>>> Try to „rm -rf ~/.cache/duplicity” the run duplicity without
>>> „--archive-dir” nor „--name”.
>> No problem with that. It just recreates the dirs, does the resync, then
>> the collection status, no delay anywhere.
>
> Strange. I can reproduce it every time. At the end, I have three GnuPG
> processes which are:
>
> gpg --status-fd 4 --passphrase-fd 8 --logger-fd 3 --batch --no-tty
> --no-secmem-warning --use-agent --decrypt
> gpg --status-fd 4 --passphrase-fd 9 --logger-fd 3 --batch --no-tty
> --no-secmem-warning --use-agent --decrypt
> gpg --status-fd 4 --passphrase-fd 10 --logger-fd 3 --batch --no-tty
> --no-secmem-warning --use-agent --decrypt
>
> If I kill them by hand, duplicity resumes.
>
> I also tried removing everything duplicity-related and installing it
> from the PPA, but the problem persists.

If you start off with a working archive, does it do the same thing? In
other words, if the first run fails and you rerun, does the second run
fail as well? Or, is it just the first run with an empty archive?