gwibber crashed with AttributeError in action()

[kyleabaker]

Binary package hint: gwibber

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
Description: Ubuntu lucid (development branch)
Release: 10.04

2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.
gwibber:
  Installed: 2.29.90.1-0ubuntu1
  Candidate: 2.29.90.1-0ubuntu1
  Version table:
 *** 2.29.90.1-0ubuntu1 0
        500 http://us.archive.ubuntu.com lucid/main Packages
        100 /var/lib/dpkg/status

3) What you expected to happen
When clicking "Delete this message" on a tweet I expect it to be removed.

4) What happened instead
Gwibber closes unexpectedly.

ProblemType: Crash
Architecture: amd64
Date: Thu Feb 25 01:38:40 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: gwibber 2.29.90.1-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
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 80, in action
     client.model.service.PerformOp(json.dumps({
 AttributeError: 'Model' object has no attribute 'service'
Uname: Linux 2.6.32-14-generic x86_64
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.