Could not determine the upgrade (Upgrade to Maverick with nVidia card)

[Thorsten Hesemeyer]

Binary package hint: update-manager

My upgrade attempt from:
from: Ubuntu 10.04 Lucid
to: Ubuntu 10.10 Maverick
with a: Lenovo ThinkPad T61p
with: nVidia G84M [Quadro FX 570M] (rev a1) graphics card
failed due to a dependency problem of this package:

xserver-xorg-video-nouveau

Workaround
==========
Just four steps:
1. Remove the nouveau package
     sudo dpkg -P xserver-xorg-video-nouveau xserver-xorg-video-all
2. Rename xorg.conf file, or Maverick will stay with a blank screen while booting (!)
     sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf_lucid
3. Upgrade to Maverick
     System=>Administration=>Upgrade Manager
4. After upgrading install the nouveau package again:
     sudo apt-get install xserver-xorg-video-nouveau

Background
=========
There is no conflict in Lucid, but there are as soon as the Maverick repositories are enabled - so the upgrade has to fail.

Error message
===========
Could not determine the upgrade
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 non of this applies, then please report this bug against the
'update-manager' package and include the files in /var/log/dist-upgrade/ in the bug report.

Dependency Conflict Backgrounds
=========================
With maverick repositories enabled:
xserver-xorg-video-nouveau depends on xorg-video-abi-8.0 which depends on xserver-xorg-core (>=2:1.8.99.904) but 2:1.7.6-2ubuntu7.3 is installed

xserver-xorg-core:
 Conflicts: xserver-xorg-input-7
  Breaks: xserver-xorg-input-synaptics (<=1.2.2-1ubuntu4) but 1.2.2-1ubuntu4 is to be installed
  Breaks: xserver-xorg-input-vmmouse (<=1:12.6.5-4ubuntu2) but 1:12.6.5-4ubuntu2 is to be installed
 Breaks: xserver-xorg-video-6
  Breaks: xserver-xorg-video-v4l (<1:0.2.0-4ubuntu1) but 1:0.2.0-4 is to be installed

The /var/log/dist-upgrade files are attached to this bug.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: update-manager 1:0.142.21
ProcVersionSignature: Ubuntu 2.6.35-23.36-generic-pae 2.6.35.7
Uname: Linux 2.6.35-23-generic-pae i686
Architecture: i386
Date: Thu Oct 28 15:08:09 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: update-manager

[Thorsten Hesemeyer (thorsten-hesemeyer)]

/var/log/dist-upgrade/main.log

[Thorsten Hesemeyer (thorsten-hesemeyer)]

/var/log/dist-upgrade/lspci.txt

[Thorsten Hesemeyer (thorsten-hesemeyer)]

/var/log/dist-upgrade/term.log is an empty file.

And finally a screen shot of error message.

Kind regards,
Thorsten Hesemeyer

[Thorsten Hesemeyer (thorsten-hesemeyer)]

Please re-enable the "restricted" repository if you want proprietary nVidia hardware drivers again:

System=>Synaptic=>Package Manager=>Settings=>Repositories
and mark the "Proprietary drivers for devices (restricted)" box again.

Enable drivers via
System=>Administration=>Additional Hardware

[William (Mike) Alam (commerce-fastmail)]

Same problem with NVIDA GeForce 8800 GT on an Intel desktop system. Can't tell if the above fix works as I am new to Linux and want to make sure I understand what I'm doing before I do it. :)

[William (Mike) Alam (commerce-fastmail)]

the's workaround worked. One glitch, step four did not take (not the right driver?) However, Compiz or (OGL?) is smart enough to find the right nVidia driver when you try to set visual effects to extra. This is probably the easiest way. System / Preferences / Appearance / Visual Effects

[Brian Murray (brian-murray)]

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 721306, 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.