E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

[Huzvar]

This can be caused by: ^M
* Upgrading to a pre-release version of Ubuntu ^M
* Running the current pre-release version of Ubuntu ^M
* Unofficial software packages not provided by Ubuntu ^M
^M
If none of this applies, then please report this bug against the ^M
'update-manager' package and include the files in ^M
/var/log/dist-upgrade/ in the bug report.

[Jean-Baptiste Lallement (jibel)]

Thanks for your report.

This is what causes the problem:
Broken libdrm-nouveau1a:i386 Breaks on libdrm-nouveau1 [ i386 ] < 2.4.23+git20110119.550fe2ca-0ubuntu0sarvatt~lucid > ( libs )
  Considering libdrm-nouveau1:i386 80 as a solution to libdrm-nouveau1a:i386 15
  Holding Back libdrm-nouveau1a:i386 rather than change libdrm-nouveau1:i386

Please install Xorg from the official Ubuntu repository before upgrading.

I'm closing this report because it is not a bug with Ubuntu.

[Huzvar (huzvar)]

I install Xorg from ubuntu repository and this dont resolve my problem.
I attach new logs

[Jean-Baptiste Lallement (jibel)]

You still have libdrm-nouveau1 from xorg-edgers installed. Please install 2.4.21-1ubuntu2.1 from maverick-updates instead. Thanks.

[Huzvar (huzvar)]

I install libdrm-nouveau1, libdrm-intel1, libdrm2, libdrm-radeon1 version 2.4.21-1ubuntu2.1.
I attach new logs

[Jean-Baptiste Lallement (jibel)]

libgl1-mesa-dri 7.11.0+git20110222.7aeb610f-0ubuntu0sarvatt~maverick is still on the way.

You can use ppa-purge to revert to the official packages or attach the file /var/lib/dpkg/status if you still have this problem after fixing libgl1-mesa-dri

[Joan G. (joan-ac)]

I am afraid that I'm in front of a similar situation.

According to my apt.log:

Broken libdrm-nouveau1a:i386 Rompe on libdrm-nouveau1 [ i386 ] < 2.4.25~glasen~maverick~ppa1 > ( libs )
  Considering libdrm-nouveau1:i386 70 as a solution to libdrm-nouveau1a:i386 13
  Holding Back libdrm-nouveau1a:i386 rather than change libdrm-nouveau1:i386
Broken keyboard-configuration:i386 Depende on upstart-job [ i386 ] < none > ( none )
  Considering upstart:i386 61 as a solution to keyboard-configuration:i386 48
  Holding Back keyboard-configuration:i386 rather than change upstart-job:i386
Broken ecryptfs-utils:i386 Depende on upstart-job [ i386 ] < none > ( none )
  Considering upstart:i386 61 as a solution to ecryptfs-utils:i386 34
  Holding Back ecryptfs-utils:i386 rather than change upstart-job:i386
Broken console-setup:i386 Depende on keyboard-configuration [ i386 ] < none -> 1.57ubuntu20 > ( utils )
  Considering keyboard-configuration:i386 48 as a solution to console-setup:i386 19
  Holding Back console-setup:i386 rather than change keyboard-configuration:i386
Broken xserver-xorg-core:i386 Depende on keyboard-configuration [ i386 ] < none -> 1.57ubuntu20 > ( utils )
  Considering keyboard-configuration:i386 48 as a solution to xserver-xorg-core:i386 69
  Holding Back xserver-xorg-core:i386 rather than change keyboard-configuration:i386
Broken xserver-xorg-input-evdev:i386 Depende on xorg-input-abi-12 [ i386 ] < none > ( none )
  Considering xserver-xorg-core:i386 69 as a solution to xserver-xorg-input-evdev:i386 6
  Holding Back xserver-xorg-input-evdev:i386 rather than change xorg-input-abi-12:i386
Broken xserver-xorg-input-wacom:i386 Depende on xorg-input-abi-12 [ i386 ] < none > ( none )
  Considering xserver-xorg-core:i386 69 as a solution to xserver-xorg-input-wacom:i386 2
  Holding Back xserver-xorg-input-wacom:i386 rather than change xorg-input-abi-12:i386
Broken xserver-xorg-video-mga:i386 Depende on xorg-video-abi-10 [ i386 ] < none > ( none )
  Considering xserver-xorg-core:i386 69 as a solution to xserver-xorg-video-mga:i386 0
  Holding Back xserver-xorg-video-mga:i386 rather than change xorg-video-abi-10:i386
Investigating (9) xserver-xorg-video-openchrome [ i386 ] < 1:0.2.904+svn842-0ubuntu1 -> 1:0.2.904+svn916-1build1 > ( x11 )
Broken xserver-xorg-video-openchrome:i386 Depende on xorg-video-abi-10 [ i386 ] < none > ( none )
  Considering xserver-xorg-core:i386 69 as a solution to xserver-xorg-video-openchrome:i386 0
  Holding Back xserver-xorg-video-openchrome:i386 rather than change xorg-video-abi-10:i386
Broken xserver-xorg-video-vmware:i386 Depende on xorg-video-abi-10 [ i386 ] < none > ( none )
  Considering xserver-xorg-core:i386 69 as a solution to xserver-xorg-video-vmware:i386 0
  Holding Back xserver-xorg-video-vmware:i386 rather than change xorg-video-abi-10:i386
Broken xserver-xorg-video-geode:i386 Depende on xorg-video-abi-10 [ i386 ] < none > ( none )
  Considering xserver-xorg-core:i386 69 as a solution to xserver-xorg-video-geode:i386 0
  Holding Back xserver-xorg-video-geode:i386 rather than change xorg-video-abi-10:i386
Investigating (9) fglrx [ i386 ] < none -> 2:8.840-0ubuntu4 > ( restricted/misc )
Broken fglrx:i386...

[Jean-Baptiste Lallement (jibel)]

@Joan please revert xserver-xorg-core 2:1.9.2.901+git20101129+server-1.9-branch.65f2ab20-0ubuntu0sarvatt2~maverick and libdrm-nouveau1 2.4.25~glasen~maverick~ppa1 and next time, please file a new bug instead. Thanks.

[Joan G. (joan-ac)]

First of all, I'm sorry for my rudeness in the first message I posted...
@Jean I do really appreciate you help, however it didn't work or I didn't know how to do it
but I've followed your suggestion and I've posted a new bug (https://bugs.launchpad.net/ubuntu/+bug/775700)!

Thank you very much for your help!

Joan

[Huzvar (huzvar)]

Problem solved

[Eliah Kagan (degeneracypressure)]

This does not appear to be an actual bug, so Fix Committed is not an appropriate status. I'm reverting the status back to Incomplete, and once it's determined that what Joan is experiencing isn't a bug either, then we can mark this bug as Invalid.

[Eliah Kagan (degeneracypressure)]

To clarify: Huzvar's problem appears to have been caused by "Unofficial software packages not provided by Ubuntu", which is one of the things that has to be ruled out in order to assume that this error is a bug. I think it's likely a similar situation for Joan, but I don't want to mark this Invalid if there's any possibility that her problem is caused by an actual bug.

@Jean-Baptiste Lallement
If, in your judgment, Joan's situation is fully addressed and definitely not a bug, then I would have no objection to your marking this Invalid now.

[Jean-Baptiste Lallement (jibel)]

I replied to Joan in his bug report and this one is fixed. I'm closing it.

Don't hesitate to submit any new bug.

[Artur Hubert (artur-hubert)]

I have problems to upgrade from 10.10 to 11.04. I get also the same error on calculating changes.
I followed this, but didn't get how to call ppa-purge to resolve the problem
Attached is the main.log, any suggestions?

[Artur Hubert (artur-hubert)]

And here the apt.log

[Eliah Kagan (degeneracypressure)]

@Artur Hubert
First install the package called ppa-purge, then run the utility from the Terminal. This documentation should help: http://manpages.ubuntu.com/manpages/maverick/en/man1/ppa-purge.1.html

[Artur Hubert (artur-hubert)]

ppa-purge already installed, but do I have to purge to be able to upgrade?

ar@ubu:~$ sudo ppa-purge xorg-edgers
PPA to be removed: xorg-edgers ppa
Warning: Could not find package list for PPA: xorg-edgers ppa

Which ppa is causing the problem during my upgrade?

[Eliah Kagan (degeneracypressure)]

@Artur Hubert
You can see what PPA's you're likely to have software installed using one of these two methods:

(1) Open the Update Manager, click Settings... on the lower left corner of the window to bring up the Software Sources window, and click the Other Software tab.

(2) Run the command "ls -l /etc/apt/sources.list.d" (without the quotes) in the Terminal.

You can purge them before the upgrade, then (assuming they support Natty), re-add them afterwards.

[Jean-Baptiste Lallement (jibel)]

@Artur, this is because your problem is caused by dontzap not a PPA. Please remove dontzap and try to upgrade again. In the future please file a new report instead of adding me too to an existing report which looks the same and actually isn't.

Thanks and don't hesitate to report any new bug.

[Sharjeel Lasharie (sharjeel)]

Same problem here:
could someone please help. Attaching the log files

[Sharjeel Lasharie (sharjeel)]

And the apt.log

[Artur Hubert (artur-hubert)]

@Jean-Baptiste Lallement
Unfurtunately I couldn't test your suggestion, because I did the Upgrade by using the USB Installation image.
Thanks anyway!

[Eliah Kagan (degeneracypressure)]

@Artur Hubert
Jean-Baptiste Lallement's suggestion was to remove the package called dontzap. Your ability to do this should not be affected in any way by the way in which you attempted to perform the upgrade, unless the process of attempting to upgrade has rendered your Ubuntu system unbootable. Please remove the package called dontzap and try again to upgrade, or explain why you are unable to remove that package.

[Eliah Kagan (degeneracypressure)]

@Sharjeel Lasharie
To get help, please submit a question (https://launchpad.net/ubuntu/+source/update-manager/+addquestion), or follow Jean-Baptiste Lallement's advice in post #24 in this bug. If you submit a question, normally you'd (1) include the full text of those files in your question, (2) add the full text of those files as comments to your question, or (3) post the files (separately) at http://paste.ubuntu.com and add them to your question. But since you've already attached them to this bug, if you start a new question, you can just link to them in your question (https://launchpadlibrarian.net/71434850/main.log and https://launchpadlibrarian.net/71434879/apt.log).

[Sharjeel Lasharie (sharjeel)]

@Eliah
Jean-Baptiste Lallement's suggestion was to remove the package called dontzap... I do not have a package called dontzap but still have that problem.

[Eliah Kagan (degeneracypressure)]

@Sharjeel Lasharie
The advice I was referring to was: "In the future please file a new report..."
https://help.ubuntu.com/community/ReportingBugs
Or open a question:
https://launchpad.net/ubuntu/+source/update-manager/+addquestion

[Artur Hubert (artur-hubert)]

@Eliah Kagan
It looks like the package isn't there any more.

sudo apt-get remove dontzap
[sudo] password for artur:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package dontzap

sudo aptitude remove dontzap
Couldn't find any package whose name or description matched "dontzap"
Couldn't find any package whose name or description matched "dontzap"
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

[Eliah Kagan (degeneracypressure)]

@Artur Hubert
As I recommended to Sharjeel Lasharie, I recommend that you either post a question about this problem (https://launchpad.net/ubuntu/+source/update-manager/+addquestion), or post a new bug report as Jean-Baptiste Lallement instructed. (Either way, I recommend you include a summary of the actions you've taken so far, and link back to this bug.)

To be clear, there is no reason to think that the precise causes of your problem and of Sharjeel Lasharie's problem are the same--so even if Sharjeel Lasharie has created a new question or bug, you should still make your own (though you might look in Sharjeel's, to see if maybe a solution there works for you).

[William E Waterman (billewaterman)]

I'm having the same problem upgrading from 11.04 to 11.10.
Here's my log.