update-manager crashed with TypeError in confirmChanges(): glib.markup_escape_text() takes at most 1 argument (2 given)

[Ben Mellor]

I started update-manager, and it told me there were distribution updates (I'm running the Oneiric beta). But it said not everything could be installed, and asked if I wanted to do a partial update.

I clicked "partial update", then it started on with the distro upgrade screen, stayed at the "calculating changes" step for a while, then reported that a required package "Ubuntu Desktop" couldn't be installed.

I clicked the close button, got a dialog saying that a system problem had happened and asking if I wanted to report it. Clicking "yes" then resulted in another dialog saying that "Update Manager closed unexpectedly". This bug post is the result of hitting "Report Problem" on that dialog.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: update-manager 1:0.152.17
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
Date: Mon Sep 12 22:34:01 2011
ExecutablePath: /usr/bin/update-manager
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/update-manager --dist-upgrade
PythonArgs: ['/usr/bin/update-manager', '--dist-upgrade']
SourcePackage: update-manager
Title: update-manager crashed with TypeError in confirmChanges(): glib.markup_escape_text() takes at most 1 argument (2 given)
UpgradeStatus: Upgraded to oneiric on 2011-09-12 (0 days ago)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #842392, so 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.