failed to upgrade from 11.04 to 11.10

[kxw102]

An unresolvable problem occurred while calculating the upgrade:
E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

 This can be caused by:
 * Upgrading to a pre-release version of Ubuntu
 * Running the current pre-release version of Ubuntu
 * Unofficial software packages not provided by Ubuntu

If none of this applies, then please report this bug using the command 'ubuntu-bug update-manager' in a terminal.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.150.3
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic-pae 2.6.38.8
Uname: Linux 2.6.38-11-generic-pae i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Fri Oct 28 01:55:21 2011
DpkgHistoryLog.txt:

DpkgTerminalLog.txt:

GConfNonDefault:
 /apps/update-manager/check_new_release_ignore=
 /apps/update-manager/first_run=false
 /apps/update-manager/window_size=(761,512)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager
UpgradeStatus: Upgraded to natty on 2011-10-27 (0 days ago)

[kxw102 (kxw0908)]

How to solve it?

[Phil. V (philip.v)]

Sorry, I meant to add a comment. Could you please attach the files in "/var/log/dist-upgrade/" to this report? They will aid in diagnosing the problem and determining how to fix it. Thanks in advance!

[kxw102 (kxw0908)]

Yes, I opened the /var/log/dist-upgrade/20111028-1326. There are 3 files: apt.log, main.log, term.log.

[kxw102 (kxw0908)]

another file: main.log

[Phil. V (philip.v)]

Could you please attach term.log as well?

[kxw102 (kxw0908)]

That file is empty, I just checked.

[Jean-Baptiste Lallement (jibel)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 874220, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.