Upgrade 6.10->7.04 fails in the start with dbus and PGP errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: update-manager
I wanted to upgrade my Ubuntu Desktop 6.10 system to the new Release 7.04 according to the roadmap on the Ubuntu website.
I verified that all system updates were done in Synaptics and that the required version of update-manager was present (i have 0.45.4), and then started update Manager from the K-Menu, as recommended.
Unfortunately, there was no message "new release 7.04 available" and no button "Upgrade" available within the message box, which was telling me that my system was up to date.
I tried then to start the upgrade directly in a gksu shell and got a popup window from update manager, offering me the system release 7.04 upgrade. But doing this ended quickly with a PGP error when checking the feisty tarball:
gksu "update-manager -c"
warning: could not initiate dbus
extracting '/tmp/tmpHvq79F
authenticate '/tmp/tmpHvq79F
'/tmp/tmpHvq79F
exception from gpg: GnuPG exited non-zero, with code 8323072
doing the same thing as sudo didn't work either:
sudo update-manager -c -d
Password:
warning: could not initiate dbus
Unhandled exception in thread started by <bound method
MetaRelease.
(UpdateManager+
Traceback (most recent call last):
File "/usr/lib/
line 170, in download
f=open(
IOError: [Errno 13] Permission denied:
'/home/
running with the --dist-ugprade option failed also, telling me that it
was trying to upgrade to 6.10 and, after 5 seconds, that my system was
up to date.
Looking for similar bug reports on launchpad I found out that a similar problem has been desribed in BUG #120957, fixed by a update manager patch. Looking into the patch I found it was already implemented in my
/usr/
and that the second patch was intended for
update-
which I do not have installed.
My Ubuntu System 6.10 was a fresh install in May 2007, on an x386 PC.
I wanted to upgrade because I need KDE 3.5.7 to be able to login to our Solaris 10 network.
The latest KDE release supported by Edgy seems to be 3.5.5, which I already have but crashes when used for a Solaris 10 login..
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.