gwibber closed unexpectedly after opening from the indicator applet

[Budoc]

Binary package hint: gwibber

Upon opening gwiiber from the indicator applet, I got a notification from apport that gwibber unexpectedly closed. I am using gwibber from Maverick-proposed.

lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10

apt-cache policy gwibber
gwibber:
  Installed: 2.32.2-0ubuntu1
  Candidate: 2.32.2-0ubuntu1
  Version table:
     2.32.2-0ubuntu2 0
        400 http://gb.archive.ubuntu.com/ubuntu/ maverick-proposed/main i386 Packages
 *** 2.32.2-0ubuntu1 0
        900 http://gb.archive.ubuntu.com/ubuntu/ maverick-updates/main i386 Packages
        100 /var/lib/dpkg/status
     2.32.0.1-0ubuntu1 0
        500 http://gb.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages

What I expected to happen: Gwibber to open without apport reporting anything

What happened instead; Apport popped up a notification stating that gwibber had closed unexpectedly and to submit a bug report to the developers.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gwibber 2.32.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic i686
Architecture: i386
Date: Tue Nov 30 02:49:28 2010
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 SHELL=/bin/zsh
 LANG=en_GB.utf8
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with AttributeError in set_overlay_text()
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 #647406, 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.