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

[Slick]

This Crashed upon login

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: apport-gtk 1.22.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic i686
Architecture: i386
CrashReports:
 600:1000:1000:44396:2011-09-06 21:37:27.645170000 -0500:2011-09-06 21:58:37.333707347 -0500:/var/crash/_usr_bin_update-notifier.1000.crash
 600:1000:1000:14680339:2011-09-05 10:41:59.003217000 -0500:2011-09-05 10:42:04.813645111 -0500:/var/crash/_usr_bin_pidgin.1000.crash
 600:104:108:641323:2011-09-06 21:57:03.586935000 -0500:2011-09-06 21:58:32.052323148 -0500:/var/crash/_usr_lib_gnome-settings-daemon_gnome-settings-daemon.104.crash
 600:1000:1000:28331:2011-09-06 21:37:27.781170000 -0500:2011-09-06 21:58:42.399198477 -0500:/var/crash/_usr_share_apport_apport-gtk.1000.crash
 600:1000:1000:49178:2011-09-05 18:50:14.220865000 -0500:2011-09-06 21:58:47.344749013 -0500:/var/crash/_usr_share_software-center_software-center-gtk3.1000.crash
Date: Tue Sep 6 21:37:28 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/share/apport/apport-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gtk
ProcEnviron:
 PATH=(custom, no 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: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin 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.