update-manager -d fails to upgrade from 6.10 to 7.04 due to download problems

Can you please attach the files in /var/log/dist-upgrade. Please also check /var/crash for an update-manager crash log.

Hi,
I again ran the update-manager:

hirsch@ueshiba:~$ gksu "update-manager -d"
GNOME_SUDO_PASS
sudo: 1 incorrect password attempt
sn_launcher_context_initiate called twice for the same SnLaunchContext
warning: could not initiate dbus
extracting '/tmp/tmpAso_mU/feisty.tar.gz'
authenticate '/tmp/tmpAso_mU/feisty.tar.gz' against '/tmp/tmpAso_mU/feisty.tar.gz.gpg'
exception from gpg: GnuPG exited non-zero, with code 131072

After getting the authentication error I'm "normally" able to close the update-manager app by hitting the close button. The app doesn't crash, it just pops up the message.

Attached files:
root@ueshiba:/var/log/dist-upgrade# ls -al
insgesamt 688
drwxr-xr-x 2 root root 4096 2006-10-18 11:07 .
drwxr-xr-x 16 root root 4096 2007-02-01 12:43 ..
-rw-r--r-- 1 root root 169423 2006-10-18 15:16 apt.log
-rw-r--r-- 1 root root 44132 2006-10-18 16:12 main.log
-rw-r--r-- 1 root root 467632 2006-10-18 16:12 term.log
root@ueshiba:/var/log/dist-upgrade#

There's no entry for apt in /var/crash:
root@ueshiba:/var/crash# ls -al
insgesamt 9096
drwxr-xr-x 2 root root 4096 2007-02-01 12:44 .
drwxr-xr-x 16 root root 4096 2007-02-01 12:43 ..
-rw------- 1 hirsch hirsch 9288561 2007-01-31 11:50 _usr_lib_firefox_firefox-bin.1000.crash
root@ueshiba:/var/crash#

I can confirm this bug. My log files are very similar to Hugo's

Command line output:

$ gksu "update-manager -d"
warning: could not initiate dbus
extracting '/tmp/tmppEE0Ms/feisty.tar.gz'
authenticate '/tmp/tmppEE0Ms/feisty.tar.gz' against '/tmp/tmppEE0Ms/feisty.tar.gz.gpg'
exception from gpg: GnuPG exited non-zero, with code 131072

This sounds like a duplicate of

https://launchpad.net/ubuntu/+source/update-manager/+bug/78673

Could you please check if using the update-manager from edgy-proposed fixes the problem for you? Or using the workaround described in the bugreport?

Thanks,
 Michael

It appears to be a duplicate of 78673, although for me it was failing with no /root/.gnupg directory rather than ~/.gnupg

I filled a duplicate (#88884, sorry), got the exact same error message, and i can confirm that typing

sudo mkdir /root/.gnupg

fixed the problem. i was confused because i do have ~/.gnupg for my sudoer user.