gwibber crashed with TypeError in on_action()

[Anand Kumria]

Binary package hint: gwibber

1)
eve:[~]% lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04

2)
eve:[~]% apt-cache policy gwibber
gwibber:
  Installed: 2.29.1-0ubuntu1
  Candidate: 2.29.1-0ubuntu1
  Version table:
 *** 2.29.1-0ubuntu1 0
        500 http://uk.archive.ubuntu.com lucid/universe Packages
        100 /var/lib/dpkg/status

3)

I clicked on a twitter style #link, and a crash dialog appeared.

gwibber:/tag?acct=23c40035e398b70e6202880e92fcbbf5&query=flybe

No crash occurs when 'Open in new window' is selected - only when 'Open link' is clicked.

4)

The link to open in as appropriate.

ProblemType: Crash
Architecture: i386
Date: Sat Feb 13 22:20:09 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
Package: gwibber 2.29.1-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANGUAGE=en_AU.utf8
 PATH=(custom, no user)
 LANG=en_AU.utf8
 SHELL=/usr/bin/zsh
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with TypeError in on_action()
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python2.6/dist-packages/gwibber/client.py", line 362, in on_action
     getattr(actions, cmd).action(None, self, **query)
 TypeError: action() got an unexpected keyword argument 'acct'
Uname: Linux 2.6.32-13-generic i686
UserGroups: admin audio camera cdrom dialout dip disk fax floppy fuse libvirtd lpadmin netdev plugdev powerdev sambashare scanner tape video

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