apport-gtk crashed with TypeError in ui_present_crash(): glib.markup_escape_text() takes at most 1 argument (2 given)

[Jeff Licquia]

Updated today. Couldn't update with update-manager; it needed to do the "partial upgrade", and got into a looping failure. Upgraded with apt-get instead.

After rebooting and logging in, it then wanted to report a number of problems, including with synergyc (which still seems to be working, despite the "crash"), and something with gsettings. When attempting to report the gsettings problem, the problem reporting system itself appeared to crash.

I ended up aborting the report on gsettings, because I wasn't confident the problem reporter was collecting the right data. I had to cancel the other problem reports a few times before they went away completely.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: apport-gtk 1.22.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
ApportLog:

ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
Date: Fri Sep 9 13:24:48 2011
ExecutablePath: /usr/share/apport/apport-gtk
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/share/apport/apport-gtk']
SourcePackage: apport
Title: apport-gtk crashed with TypeError in ui_present_crash(): glib.markup_escape_text() takes at most 1 argument (2 given)
UpgradeStatus: Upgraded to oneiric on 2011-09-09 (0 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare

[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 #833592, 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.