twitter.py: TypeError: string indices must be integers

[Captain Chaos]

Binary package hint: gwibber

Gwibber has stopped updating my Twitter feed again. This time the error message I get when running gwibber-service -do is:

Gwibber Dispatcher: ERROR <twitter:receive> Operation failed
Gwibber Dispatcher: DEBUG Traceback:
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/dispatcher.py", line 75, in perform_operation
    message_data = PROTOCOLS[account["protocol"]].Client(account)(opname, **args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 146, in __call__
    return getattr(self, opname)(**args)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 149, in receive
    return self._get("statuses/home_timeline.json", count=count, since_id=since)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 137, in _get
    if parse: return [getattr(self, "_%s" % parse)(m) for m in data]
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 80, in _message
    m = self._common(data)
  File "/usr/lib/python2.6/dist-packages/gwibber/microblog/twitter.py", line 62, in _common
    m["id"] = str(data["id"])
TypeError: string indices must be integers

And the same happens for the <twitter:responses> and <twitter:private> operations. This has started happening since this morning, without any updates having been installed.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gwibber 2.30.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Sep 1 13:26:39 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
PackageArchitecture: all
SourcePackage: gwibber

[Omer Akram (om26er)]

try gwibber 2.30.2 from this ppa https://launchpad.net/~ubuntu-desktop/+archive/ppa

[Captain Chaos (launchpad-chaos)]

Yup, Twitter is working again with version 2.30.2, so the bug appears to have been fixed in that version. Although of course it could just be coincidence, because so many of these bugs are triggered by specific tweets and the offending tweet may have fallen of my feed in the mean time...