Crashes with encryption password error message

[Graeme]

On first use the system scanned my files but did not create a backup. Error message was similar to "Bad encryption password". There does not appear to be a facility to change the password and there is no explanation of why it is not acceptable. This should be checked when password is first entered?
File /tmp/deja-dup.log was created by your command but is empty. Command never completed. Command was copied and pasted so this is not a typo. I tried twice, including copy and paste.
File /tmp/deja-dup.gconf follows
<gconfentryfile>
  <entrylist base="/apps/deja-dup">
    <entry>
      <key>backend</key>
      <schema_key>/schemas/apps/deja-dup/backend</schema_key>
      <value>
        <string>file</string>
      </value>
    </entry>
    <entry>
      <key>delete-after</key>
      <schema_key>/schemas/apps/deja-dup/delete-after</schema_key>
      <value>
        <int>56</int>
      </value>
    </entry>
    <entry>
      <key>encrypt</key>
      <schema_key>/schemas/apps/deja-dup/encrypt</schema_key>
      <value>
        <bool>true</bool>
      </value>
    </entry>
    <entry>
      <key>exclude-list</key>
      <schema_key>/schemas/apps/deja-dup/exclude-list</schema_key>
      <value>
        <list type="string">
            <value>
              <string>$TRASH</string>
            </value>
            <value>
              <string>/proc</string>
            </value>
            <value>
              <string>/sys</string>
            </value>
            <value>
              <string>/tmp</string>
            </value>
            <value>
              <string>/var/cache</string>
            </value>
            <value>
              <string>/var/tmp</string>
            </value>
            <value>
              <string>/dev</string>
            </value>
        </list>
      </value>
    </entry>
    <entry>
      <key>include-list</key>
      <schema_key>/schemas/apps/deja-dup/include-list</schema_key>
      <value>
        <list type="string">
            <value>
              <string>$HOME</string>
            </value>
            <value>
              <string>/home/graeme/Desktop</string>
            </value>
            <value>
              <string>/media/Multimedia/Music</string>
            </value>
            <value>
              <string>/media/Multimedia/Pictures</string>
            </value>
            <value>
              <string>/media/Data</string>
            </value>
            <value>
              <string>/var</string>
            </value>
            <value>
              <string>/usr/local</string>
            </value>
            <value>
              <string>/etc</string>
            </value>
        </list>
      </value>
    </entry>
    <entry>
      <key>last-run</key>
      <schema_key>/schemas/apps/deja-dup/last-run</schema_key>
      <value>
        <string>2010-03-01T06:55:07.933252Z</string>
      </value>
    </entry>
    <entry>
      <key>periodic</key>
      <schema_key>/schemas/apps/deja-dup/periodic</schema_key>
      <value>
        <bool>false</bool>
      </value>
    </entry>
    <entry>
      <key>periodic-period</key>
      <schema_key>/schemas/apps/deja-dup/periodic-period</schema_key>
      <value>
        <int>7</int>
      </value>
    </entry>
    <entry>
      <key>file/path</key>
      <schema_key>/schemas/apps/deja-dup/file/path</schema_key>
      <value>
        <string>/media/ext3Backup</string>
      </value>
    </entry>
    <entry>
      <key>s3/bucket</key>
      <schema_key>/schemas/apps/deja-dup/s3/bucket</schema_key>
    </entry>
    <entry>
      <key>s3/folder</key>
      <schema_key>/schemas/apps/deja-dup/s3/folder</schema_key>
      <value>
        <string>/</string>
      </value>
    </entry>
    <entry>
      <key>s3/id</key>
      <schema_key>/schemas/apps/deja-dup/s3/id</schema_key>
    </entry>
  </entrylist>
</gconfentryfile>
Version numbers follow
deja-dup 11.1-0ubuntu0karmic1
duplicity 0.6.06-0ubuntu0karmic1
Description: Ubuntu 9.10

My system is up to date.

Regards

Graeme

[Michael Terry (mterry)]

Hrm. You can see if Deja Dup is keeping a password which it will automatically use by going to "Applications->Accessories->Passwords and Encryption Keys". There you can tell the system to forget about saved passwords. Do that and try backing up again.

I'm not sure why you would get that message on your first backup. Sounds like Deja Dup was trying to add to a backup that either didn't have a password or had a different one. Are there any backup files in the target directory (files called duplicity-*)?

[Graeme (graeme-wyatt)]

Thanks Michael

There was an entry for Deja Dup in the password list which I deleted. I
did not tell the system to forget about saved passwords as I find the
feature very useful however I did not select Save Password when I tried
Deja Dup again and I have checked to ensure that there is no entry for
it in the password list. However I still got the same error.

The target directory is a partition on external hard drive and has some
other backup files on it created by Simple Backup. These do not include
the word duplicity but are named like
"2010-03-04_17.32.14.260477.Nookawarra.inc". These files do not have
passwords.

Regards

Graeme

Michael Terry wrote:
> Hrm. You can see if Deja Dup is keeping a password which it will
> automatically use by going to "Applications->Accessories->Passwords and
> Encryption Keys". There you can tell the system to forget about saved
> passwords. Do that and try backing up again.
>
> I'm not sure why you would get that message on your first backup.
> Sounds like Deja Dup was trying to add to a backup that either didn't
> have a password or had a different one. Are there any backup files in
> the target directory (files called duplicity-*)?
>
> ** Changed in: deja-dup
> Status: New => Incomplete
>
>

[Michael Terry (mterry)]

OK. So it isn't anything obvious. I think I will need to see the log. But you say it was empty...

When you ran the command, did you then try to backup? The Deja Dup window will come up and you should be able to replicate the error. Then the log file *should* be filled with info.

If you did replicate the error and the log file is still empty... It has to be something going crazy wrong inside Deja Dup itself, but I'm not sure what. Does it happen to work if you don't use encryption?

[Graeme (graeme-wyatt)]

It appears that I was in stupid mode and did not ry to backup after
running the log command. I have now done so, replicated the error and
attach the log file.

YES!! it works if I don't use encryption. It created tar files named
duplicity-full.20100308T104049Z.vol1.difftar.gz to
duplicity-full.20100308T104049Z.vol592.difftar.gz, each 30MB plus
vol593 at 10.3 MB and 2 additional files named
duplicity-full-signatures.20100308T104049Z.sigtar.gz and
duplicity-full.20100308T104049Z.manifest.

This is a total of some 18 GB for a set of directories which total
25.8GB - not a great deal of compression.

The system at one stage got stuck on an iso file that I had mistakenly
placed in a directory that was to be backed up. This file was probably
corrupt but DejaDup created over 100 tar files for this single iso that
was less than 100MB. I did not attempt to back up any other iso files
but it also failed on a vid file in .virtualbox.

Hope the above helps

Regards

Graeme

Michael Terry wrote:
> OK. So it isn't anything obvious. I think I will need to see the log.
> But you say it was empty...
>
> When you ran the command, did you then try to backup? The Deja Dup
> window will come up and you should be able to replicate the error. Then
> the log file *should* be filled with info.
>
> If you did replicate the error and the log file is still empty... It
> has to be something going crazy wrong inside Deja Dup itself, but I'm
> not sure what. Does it happen to work if you don't use encryption?
>
>

[Michael Terry (mterry)]

The GPG error looks like this bit from the logs:

GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: failed to create temporary file `/home/graeme/.gnupg/.#lk0x8a9ee20.Nookawarra.5208': Permission denied
gpg: keyblock resource `/home/graeme/.gnupg/pubring.gpg': general error
gpg: can't open `/home/graeme/.gnupg/random_seed': Permission denied
gpg: note: random_seed file not updated
===== End GnuPG log =====

So some permission issues with ~/.gnupg?

[Peter Bojtos (peter-bojtos)]

I'm having the same problem, but i'm using an other version of deja-dup (Déjà Dup 14.1). My problem is, that i can't find any log files in the /tmp folder. (OS: Fedora 13 Beta with kernel 2.6.33.3-85.fc13.x86_64 #1 SMP x86_64 x86_64 x86_64 GNU/Linux)
The backup partition is formatted just before trying to make an encrypted backup, so there aren't any older backups stored there.
I've tried to erase all of my stored passwords in the Apps/Accessories/PWD, but it can't help.
I also tried to erase the ~/.gnupg folder, but it also didn't make things better.

How can i get a log file from deja-dup?

Thanks,
Peter

[Graeme (graeme-wyatt)]

I simply followed Michael Terry's instructions to create a log file.
However I gave up on deja-dup for the reasons above so I have never
attempted to solve the encryption problem other than to confirm that I
did indeed have a permission problem with ~/.gnupg.

I am now using Back in Time and find it excellent.

johnny wrote:
> I'm having the same problem, but i'm using an other version of deja-dup (Déjà Dup 14.1). My problem is, that i can't find any log files in the /tmp folder. (OS: Fedora 13 Beta with kernel 2.6.33.3-85.fc13.x86_64 #1 SMP x86_64 x86_64 x86_64 GNU/Linux)
> The backup partition is formatted just before trying to make an encrypted backup, so there aren't any older backups stored there.
> I've tried to erase all of my stored passwords in the Apps/Accessories/PWD, but it can't help.
> I also tried to erase the ~/.gnupg folder, but it also didn't make things better.
>
> How can i get a log file from deja-dup?
>
> Thanks,
> Peter
>
>

[Peter Bojtos (peter-bojtos)]

The problem have almost solved itself. The duplicity said something like:
"gpg agent not implemented yet." (and 'fcourse something about the permissions on the ~/.gnupg folder)

Then I erased the /tmp/seahorse*, and now, encrypted backup works.

[Michael Terry (mterry)]

OK, I'm closing this bug. Both people experiencing the problem have moved past it (one way or another), and it seems like it was a permissions issue with their gpg setup... I don't think there's anything to do here.