checkPriority can cause problems with belocs-locales-bin if its still considered downloadable (cdrom source)

Bug #474543 reported by Don Estberg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
Medium
Unassigned
Karmic
Won't Fix
Undecided
Unassigned
Lucid
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: update-manager

I can reproduce this problem on jaunty by doing a:
$ sudo apt-cdrom add
with a ubuntu8.10-alternate-i386.iso cdrom and trying to upgrade to karmic.

However for me the fix is to comment out the cdrom source in the sources.list

Could not calculate 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 none 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.

I tried removing firefox-3.5 since that was the only thing I could think of that was not standard 9.04, but didn't help.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: update-manager 1:0.111.9
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager
Uname: Linux 2.6.28-16-generic i686

Revision history for this message
Don Estberg (destberg1) wrote :
Revision history for this message
Christopher Meiklejohn (cmeiklejohn) wrote :

Thanks for your bug report.

Can you try running apt-get install -f, report the output and try the upgrade again?

- Chris

Changed in update-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Don Estberg (destberg1) wrote :

# apt-get install -f
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
  xulrunner-1.9.1 linux-headers-2.6.28-11 libboost-thread1.34.1
  libboost-date-time1.34.1 linux-headers-2.6.28-11-generic
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 885 not upgraded.
# apt-get autoremove
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
  xulrunner-1.9.1 linux-headers-2.6.28-11 libboost-thread1.34.1
  libboost-date-time1.34.1 linux-headers-2.6.28-11-generic
The following packages will be REMOVED:
  libboost-date-time1.34.1 libboost-thread1.34.1 linux-headers-2.6.28-11
  linux-headers-2.6.28-11-generic xulrunner-1.9.1
0 upgraded, 0 newly installed, 5 to remove and 885 not upgraded.
After this operation, 97.6MB disk space will be freed.
Do you want to continue [Y/n]? (Reading database ... 230979 files and directories currently installed.)
Removing libboost-date-time1.34.1 ...
Removing libboost-thread1.34.1 ...
Removing linux-headers-2.6.28-11-generic ...
Removing linux-headers-2.6.28-11 ...
Removing xulrunner-1.9.1 ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place

Upgrade had same error - new logs attached.

Revision history for this message
Don Estberg (destberg1) wrote :
Revision history for this message
Don Estberg (destberg1) wrote :

I downloaded ubuntu-9.10-alternate-i386.iso, and used apt-cdrom to add it. Then when I bring up the update-manager it pops up

Not all updates can be installed

Run a partial upgrade, to install as many updates as possible.

This can be caused by:
* A previous upgrade that didn't complete
* Problems with some of the installed software
* Unofficial software packages not provided by Ubuntu
* Normal changes of a pre-release version of Ubuntu

When I click Partial Upgrade, it proceeds as before and ends with the same error.

When I click Close and Install Updates, then the upgrade to 9.10 completes with no errors!

Let me know if you want any logs to figure out why Update fails, but Install Updates works.

I am on 9.10, but the update-manager still has a problem: The part of the window about upgrading to 9.10 is no longer there, but I still get the same popup above about Not all updates can be installed. When I click on on Partial Upgrade, it gets the same error.

How can I get my update-manager back to a sane state?

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

It appears that the "belocs-locales-bin" package is causing those issues. This package is no longer in the archive since intrepid. Could you please try to "sudo apt-get remove --purge belocs-locales-bin" and see if that looks ok (does not want to remove much more) and if it fixes the upgrade problem.

Revision history for this message
Michael Vogt (mvo) wrote :

Could you please also run:
$ apt-cache policy belocs-locales-bin

before removing the package and attach the output here?

Revision history for this message
Michael Vogt (mvo) wrote :

This patch here might fix the issue, but I would like to get a idea about the root cause of it first (hence the apt-cache policy output).

=== modified file 'DistUpgrade/DistUpgradeCache.py'
--- DistUpgrade/DistUpgradeCache.py 2009-10-09 13:26:52 +0000
+++ DistUpgrade/DistUpgradeCache.py 2009-11-06 08:58:57 +0000
@@ -557,7 +557,10 @@
                 not (pkg.isInstalled or pkg.markedInstall) and
                 not pkg.name in removeEssentialOk and
                 pkg.priority in need):
- self.markInstall(pkg.name, "priority in required set '%s' but not scheduled for install" % need)
+ try:
+ self.markInstall(pkg.name, "priority in required set '%s' but not scheduled for install" % need)
+ except:
+ logging.exception("markIntall failed")

     # FIXME: make this a decorator (just like the withResolverLog())
     def updateGUI(self, view, lock):

summary: - Unresolvable problem occurred while calculating the upgrade to 9.10
+ Priority check can cause problems with belocs-locales-bin if its still
+ considered downloadable (cdrom source?)
summary: - Priority check can cause problems with belocs-locales-bin if its still
+ checkPriority can cause problems with belocs-locales-bin if its still
considered downloadable (cdrom source?)
Changed in update-manager (Ubuntu Lucid):
milestone: none → lucid-alpha-1
Revision history for this message
Michael Vogt (mvo) wrote : Re: checkPriority can cause problems with belocs-locales-bin if its still considered downloadable (cdrom source?)

I add a lucid task because this will most likely affect upgrades from 8.04 -> 10.04

Revision history for this message
Don Estberg (destberg1) wrote :

# apt-cache policy belocs-locales-bin
belocs-locales-bin:
  Installed: (none)
  Candidate: 2.4-2.3ubuntu1
  Version table:
     2.4-2.3ubuntu1 0
        500 cdrom://Ubuntu 8.10 _Intrepid Ibex_ - Release i386 (20081030) intrepid/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Don Estberg (destberg1) wrote :

# apt-get remove --purge belocs-locales-bin
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package belocs-locales-bin is not installed, so not removed

Revision history for this message
Don Estberg (destberg1) wrote :

I tried removing the Ubuntu 8.10 CDROM from my sources.list, but that didn't help.

Although a lot is working on my Ubuntu 9.10, there are a half a dozen annoying problems and one critical problem (evolution https://bugzilla.gnome.org/show_bug.cgi?id=601125), so I'm hoping completing the upgrade will solve these. There are 177 packages not upgraded.

I'd appreciate suggestions of what to try next. Thanks!

Revision history for this message
Don Estberg (destberg1) wrote :

Michael,

I tried the patch in your Comment #8:

--- /usr/share/pyshared/DistUpgrade/DistUpgradeCache.py 2009-10-23 05:52:42.000000000 -0700
+++ /usr/share/pyshared/DistUpgrade/DistUpgradeCache.py.MichaelVogtPatch 2009-11-09 10:54:45.000000000 -0800
@@ -557,7 +557,10 @@
                 not (pkg.isInstalled or pkg.markedInstall) and
                 not pkg.name in removeEssentialOk and
                 pkg.priority in need):
+ try:
                 self.markInstall(pkg.name, "priority in required set '%s' but not scheduled for install" % need)
+ except:
+ logging.exception("markIntall failed")

     # FIXME: make this a decorator (just like the withResolverLog())
     def updateGUI(self, view, lock):

But I must be missing a step in installing this correctly because with this in place, the update manager doesn't come up at all. There was no error in /var/log/syslog, but again I may not know the right place to look for errors logged.

Revision history for this message
Don Estberg (destberg1) wrote :
Download full text (23.7 KiB)

When the update manager didn't come up in Comment #13, there was a python traceback in /var/crashes:

ProblemType: Crash
Date: Mon Nov 9 10:55:23 2009
ExecutablePath: /usr/bin/update-manager
InterpreterPath: /usr/bin/python2.6
ProcCmdline: /usr/bin/python2.6 /usr/bin/update-manager
ProcCwd: /home/dge
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcMaps:
 00110000-0012c000 r-xp 00000000 08:05 4572851 /usr/lib/pyshared/python2.6/gtk-2.0/gobject/_gobject.so
 0012c000-0012d000 r--p 0001b000 08:05 4572851 /usr/lib/pyshared/python2.6/gtk-2.0/gobject/_gobject.so
 0012d000-0012f000 rw-p 0001c000 08:05 4572851 /usr/lib/pyshared/python2.6/gtk-2.0/gobject/_gobject.so
 0012f000-0014a000 r-xp 00000000 08:05 4461019 /usr/lib/libatk-1.0.so.0.2809.1
 0014a000-0014b000 r--p 0001b000 08:05 4461019 /usr/lib/libatk-1.0.so.0.2809.1
 0014b000-0014c000 rw-p 0001c000 08:05 4461019 /usr/lib/libatk-1.0.so.0.2809.1
 0014c000-0014e000 r-xp 00000000 08:05 4457335 /usr/lib/libXcomposite.so.1.0.0
 0014e000-0014f000 r--p 00001000 08:05 4457335 /usr/lib/libXcomposite.so.1.0.0
 0014f000-00150000 rw-p 00002000 08:05 4457335 /usr/lib/libXcomposite.so.1.0.0
 00150000-00152000 r-xp 00000000 08:05 4459916 /usr/lib/libXdamage.so.1.1.0
 00152000-00153000 rw-p 00001000 08:05 4459916 /usr/lib/libXdamage.so.1.1.0
 00153000-00157000 r-xp 00000000 08:05 4457715 /usr/lib/libXfixes.so.3.1.0
 00157000-00158000 r--p 00003000 08:05 4457715 /usr/lib/libXfixes.so.3.1.0
 00158000-00159000 rw-p 00004000 08:05 4457715 /usr/lib/libXfixes.so.3.1.0
 00159000-00161000 r-xp 00000000 08:05 4458902 /usr/lib/libXrender.so.1.3.0
 00161000-00162000 r--p 00007000 08:05 4458902 /usr/lib/libXrender.so.1.3.0
 00162000-00163000 rw-p 00008000 08:05 4458902 /usr/lib/libXrender.so.1.3.0
 00165000-00167000 r-xp 00000000 08:05 950785 /lib/tls/i686/cmov/libutil-2.10.1.so
 00167000-00168000 r--p 00001000 08:05 950785 /lib/tls/i686/cmov/libutil-2.10.1.so
 00168000-00169000 rw-p 00002000 08:05 950785 /lib/tls/i686/cmov/libutil-2.10.1.so
 00169000-002a7000 r-xp 00000000 08:05 950479 /lib/tls/i686/cmov/libc-2.10.1.so
 002a7000-002a9000 r--p 0013e000 08:05 950479 /lib/tls/i686/cmov/libc-2.10.1.so
 002a9000-002aa000 rw-p 00140000 08:05 950479 /lib/tls/i686/cmov/libc-2.10.1.so
 002aa000-002ad000 rw-p 00000000 00:00 0
 002ad000-0033f000 r-xp 00000000 08:05 4462029 /usr/lib/libgdk-x11-2.0.so.0.1800.3
 0033f000-00341000 r--p 00092000 08:05 4462029 /usr/lib/libgdk-x11-2.0.so.0.1800.3
 00341000-00342000 rw-p 00094000 08:05 4462029 /usr/lib/libgdk-x11-2.0.so.0.1800.3
 00342000-0035a000 r-xp 00000000 08:05 4462039 /usr/lib/libgdk_pixbuf-2.0.so.0.1800.3
 0035a000-0035b000 r--p 00017000 08:05 4462039 /usr/lib/libgdk_pixbuf-2.0.so.0.1800.3
 0035b000-0035c000 rw-p 00018000 08:05 4462039 /usr/lib/libgdk_pixbuf-2.0.so.0.1800.3
 0035c000-003ef000 r-xp 00000000 08:05 4456971 /usr/lib/libgio-2.0.so.0.2200.2
 003ef000-003f0000 r--p 00092000 08:05 4456971 /usr/lib/libgio-2.0.so.0.2200.2
 003f0000-003f1000 rw-p 00093000 08:05 4456971 /usr/lib/libgio-2.0.so.0.2200.2
 003f1000-003f2000 rw-p 00000000 00:00 0
 003f2000-003f4000 r-xp 00000000...

Revision history for this message
Don Estberg (destberg1) wrote :

OK after correcting indentation, as the trace in the last comment suggested, still get the same error. The new apt.log is attached.

Revision history for this message
Don Estberg (destberg1) wrote :
Revision history for this message
Don Estberg (destberg1) wrote :

I backed out the patch, and update manager was still giving the same error. I shut it down, brought up the Synaptic Package Manager, marked packages for upgrade, and applied them, which completed with no error. Just to check, I brought up the update manager, and it is happy now.

Revision history for this message
Michael Vogt (mvo) wrote :

Hello Don,

thanks for testing the fix and for the apt-cache policy output. The bug is that the obsolete cdrom source is used
by apt/update-manager. Its odd that commenting out the cdrom source does not fix it.

Changed in update-manager (Ubuntu Lucid):
status: Incomplete → Triaged
importance: Undecided → Medium
summary: checkPriority can cause problems with belocs-locales-bin if its still
- considered downloadable (cdrom source?)
+ considered downloadable (cdrom source)
Michael Vogt (mvo)
description: updated
description: updated
Revision history for this message
Don Estberg (destberg1) wrote :

I still get the same error from the update manager, but update using the Synaptic Package Manager works (see Comment #17). Any progress on this?

Michael Vogt (mvo)
Changed in update-manager (Ubuntu Lucid):
status: Triaged → In Progress
Revision history for this message
Michael Vogt (mvo) wrote :

This patch here:

== modified file 'DistUpgrade/DistUpgrade.cfg'
--- DistUpgrade/DistUpgrade.cfg 2009-12-09 14:18:58 +0000
+++ DistUpgrade/DistUpgrade.cfg 2009-12-09 16:24:12 +0000
@@ -13,7 +13,7 @@
 MetaPkgs=ubuntu-desktop, kubuntu-desktop, xubuntu-desktop, ubuntustudio-desktop, ichthux-desktop, mythbuntu-desktop
 BaseMetaPkgs=ubuntu-minimal, ubuntu-standard
 Demotions=demoted.cfg
-RemoveEssentialOk=sysvinit, sysvutils
+RemoveEssentialOk=sysvinit, sysvutils, belocs-locales-bin
 RemovalBlacklistFile=removal_blacklist.cfg
 # if those packages were installed, make sure to keep them installed
 KeepInstalledPkgs=gnumeric, hpijs, grub

fixes the problem for me.

Revision history for this message
Michael Vogt (mvo) wrote :

(sorry that the update on this bug took so long)

Changed in update-manager (Ubuntu Lucid):
status: In Progress → Fix Committed
Steve Langasek (vorlon)
Changed in update-manager (Ubuntu Lucid):
milestone: lucid-alpha-1 → lucid-alpha-2
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-manager - 1:0.131.2

---------------
update-manager (1:0.131.2) lucid; urgency=low

  * data/release-upgrades:
    - default to lts->lts upgrade prompts for lucid
  * AutoUpgradeTester/UpgradeTestBackendQemu.py:
    - allow virtio for block devices when the virtio option
      is given in the config
  * DistUpgrade/DistUpgrade.cfg, DistUpgrade/DistUpgrade.cfg.hardy:
    - cleanup PostUpgradePurge and add "linux-restricted-modules-common"
    - cleanup ForcedObsoletes rules
    - update kernel removal rules and BaseNames
    - fix belocs-locales-bin upgrade issue (LP: #474543)
  * DistUpgrade/DistUpgradeController.py:
    - check forh reboot-required files in partial upgrade mode,
      update-notifier is no longer doing that by default
      (foundations-lucid-restart-required-dialog spec)
  * DistUpgrade/DistUpgrade.ui:
    - add a bunch of missing "<property name="orientation">"
    - improve restart-required dialog
 -- Michael Vogt <email address hidden> Mon, 14 Dec 2009 10:59:51 +0100

Changed in update-manager (Ubuntu Lucid):
status: Fix Committed → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Karmic has long since stopped to receive any updates. Marking the Karmic task for this ticket as "Won't Fix".

Changed in update-manager (Ubuntu Karmic):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.