Ubuntu
update-manager package

Update-manager could not calculate the upgrade from feisty to gutsy

Bug #191834 reported by Havard Bjastad on 2008-02-14

This bug report is a duplicate of: Bug #157763: [master] nfs-common makes upgrade calculation impossible (was: Could not calculate the upgrade). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	update-manager (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: update-manager

I upgraded from edgy ("6.10") to feisty ("7.04") yesterday. After the reboot, update-manager says that a new version ("7.10") is available. When I try to let it upgrade, it ends with this message:

Could not calculate the upgrade

A unresolvable problem occurred while calculating the upgrade.

Please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bugreport.

See original description

Tags:

Revision history for this message

Havard Bjastad (havard-bjastad) wrote on 2008-02-14:

apt.log Edit (34.2 KiB, text/plain)

Revision history for this message

Havard Bjastad (havard-bjastad) wrote on 2008-02-14:

main.log Edit (3.5 KiB, text/plain)

Revision history for this message

Havard Bjastad (havard-bjastad) wrote on 2008-02-14:

main_pre_req.log Edit (1.3 KiB, text/plain)

Revision history for this message

Havard Bjastad (havard-bjastad) wrote on 2008-02-14:

term.log is empty

Console output:
extracting '/tmp/tmpdVIi_p/gutsy.tar.gz'
authenticate '/tmp/tmpdVIi_p/gutsy.tar.gz' against '/tmp/tmpdVIi_p/gutsy.tar.gz.gpg'
could not send the dbus Inhibit signal: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Havard Bjastad (havard-bjastad) on 2008-02-14

description:

updated

Revision history for this message

Richard Birnie (rbirnie-deactivatedaccount) wrote on 2008-03-19:

Thanks for reporting this bug. The logs indicate that this is a duplicate of an already known issue that is being tracked as bug 157763. Marking this as a duplicate, please follow discussions in that thread