gwibber crashed when 'View Reply Thread' is clicked

[Adam]

Binary package hint: gwibber

I clicked the gears on one person's post and clicked 'View Reply Thread' from the context menu.
Nothing happens, and the application reports it as a crash, although the application itself does not quit.

System:
 Description: Ubuntu lucid (development branch)
Release: 10.04

gwibber:
  Installed: 2.29.92.1-0ubuntu1
  Candidate: 2.29.92.1-0ubuntu1
  Version table:
 *** 2.29.92.1-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gwibber 2.29.92.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic i686
Architecture: i386
Date: Sat Mar 27 15:45:04 2010
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with AttributeError in action()
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python2.6/dist-packages/gwibber/actions.py", line 38, in action
     tab_label = msg.original_title if hasattr(msg, "original_title") else msg.text
 AttributeError: 'dict' object has no attribute '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 #444654, 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.

[Adam (brainpwranimation)]

This is not the same bug. Bug #444654 involves a different python error than this one listed.

[Adam (brainpwranimation)]

Never mind, I didn't read all the comments.