Note: This also happens in Lucid amd64. Traceback from console:
Traceback (most recent call last):
File /usr/bin/gwibber, line 67, in module
client.Client()
File /usr/lib/python2.6/dist-packages/gwibber/client.py, line 448, in
__init__
self.w = GwibberClient()
File
[Expired for gwibber (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gwibber (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/743573
Thank you for taking the time to report this bug and helping to make Ubuntu
better,
this should be fixed in the upcoming 3.3.4 release.
** Changed in: gwibber (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: gwibber (Ubuntu)
Status: Invalid = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/743573
Title:
gwibber crashed with KeyError in render_body(): ' 0 '
To manage
Jaime, please could you check if this behaviour is still affecting you
with latest release of gwibber 3.0.0.1? Thanks.
** Visibility changed to: Public
** Changed in: gwibber (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
