gwibber crashed with KeyError in render()

[tristan8276]

Binary package hint: gwibber

Didn't see this specific KeyError listed in any other bugs as duplicate. Included apport logs.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gwibber 2.29.94-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CheckboxSubmission: 5248365ac4bba9aa29dfef429d19e9c1
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
Date: Fri Apr 2 13:00:42 2010
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with KeyError in render()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Omer Akram (om26er)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

and please dont confirm you bug reports or assign them.

[tristan8276 (tristan8276)]

Ah, sorry about that. I had read the triage guide to say that if there was sufficient information, aka apport, then a bug could be confirmed.

If this issue is of no importance then I shall remove it.

Again, apologies.

[tristan8276 (tristan8276)]

Also, as far as I know, it is not standard procedure to mark new apport bugs as incomplete, so resetting status to new.

[Bruno Girin (brunogirin)]

I just had it on my newly-upgraded laptop so marking it as confirmed.

Steps to reproduce:
1. Open Gwibber from the "envelope" menu at the top of the screen,
2. Select an account to see new messages (account imported during upgrade),
3. Gwibber keeps working but Apport detects the crash and reports it.

Expected behaviour:
No crash report from Apport

Actual behaviour:
The crash report icon appears at the top of the screen and when clicked opens apport to report this crash.

[Omer Akram (om26er)]

Thanks for the bug report. This particular bug has already been reported and is a duplicate of bug 579668 , so is being marked as such. Any further discussion regarding the bug should occur in the other report. Feel free to report any other bugs you may find.

[Dr Grischa Meyer (grischa)]

HI there,
this is not a duplicate error, and I do have a fix for this bug.
It is related to html entities in tweets and the fact that htmllib does not seem to be robust enough to handle those...
The fix I used is taken from:
http://effbot.org/zone/re-sub.htm#unescape-html

I am using the latest gwibber version 2.32.2 that comes with 10.10

Cheers

[Launchpad Janitor (janitor)]

This bug was fixed in the package gwibber - 2.91.2-0ubuntu1

---------------
gwibber (2.91.2-0ubuntu1) natty; urgency=low

  * New upstream release
    - foursquare: fails if response contains a venue that has been
      deleted (Teester) (LP: #687498)
    - dispatcher: catch exception per every failing-message (Marco
      Trevisan) (LP: #645512)
    - Dump test data (~/.cache/gwibber/dump/) if GWIBBER_TEST_DUMP=1
    - Don't use the deprecated htmllib escaping for html entities (LP: #554205)
 -- Ken VanDine <email address hidden> Tue, 14 Dec 2010 14:53:13 -0500