gwibber-service uses 100% cpu when network connection gets bad

[Henning Sprang]

When a network connections get's bad, I often see gwibber-service consuming 100% cpu. which is bad.

I would probably have to test ist, but I supect it happens only, when the network connection gets bad _without_ the interface going down or being misconfigured.

So you can't reproduce it by just shutting down the network on your machine, but you have to disconnect the network somewhere else (e.g. pulling the dsl cable from the router when working in a real network).
It happens for me for example when in a train on a umts connection which sometimes drops/gets bad without the interfaces going down.

Just now happened with Gwibber 2.32.2 from PPA on Ubuntu Lucid.