gwibber crashed with TypeError in render()

[Chris Giltnane]

Binary package hint: gwibber

started it up. profile had been set up and previously logged in to facebook.

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 6994cb75da89289d5c8beb23b87171ff
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
Date: Sat Feb 20 18:52:43 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gwibber
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: symap_custom symev_custom
Package: gwibber 2.29.90.1-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
 LC_PAPER=en_GB.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-14.19-generic
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with TypeError in render()
Uname: Linux 2.6.32-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare vboxusers video

[Omer Akram (om26er)]

Thanks for taking time to report this bug and help make ubuntu better. Can you please update your gwibber to 2.29.92 in Lucid and see if this problem is still there

[Dick Thomas (xpd259-deactivatedaccount)]

I just updated to latest version and then added my accounts and it no longer starts :(

[Mike Basinger (mike.basinger)]

Having the same problem with gwibber 2.29.92.1.

[Omer Akram (om26er)]

Mike are there any specific steps to reproduce this crash?

[Mike Basinger (mike.basinger)]

It happen randomly when launching gwibber.

[Marius Petriu (marius-xsite)]

To me it happens EVERY time I try to start it. I mention that I just installed lucid beta 1, applied all patches up to date, then wanted to start Gwibber after setting up my accounts.

[Victor Vargas (kamus)]

@Chris, Please could you upgrade to latest version of gwibber (2.29.94) and check if this problem is still affecting you? Thanks in advance!

[Victor Vargas (kamus)]

@Chris, any news about this issue? is this still affecting you? Thanks!

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!