This bug was fixed in the package gwibber - 3.2.1-0ubuntu1.2
---------------
gwibber (3.2.1-0ubuntu1.2) oneiric-proposed; urgency=low
* debian/patches/lp_861903.patch
- Revert fix for bug 812039 which caused a loop which drives CPU usage up
when the entry is being displayed. (LP: #861903)
gwibber (3.2.1-0ubuntu1.1) oneiric-proposed; urgency=low
* New upstream release
- don't block the UI loading when creating the model (LP: #864727)
- Add an index to speed up retrieving messages (LP: #864727)
- Added profiling output
- only disconnect valid handlers
- lens: ensure we refresh the results when the lens becomes active, but
only if the stream_model has changed
- lens: don't clear the results model on an invalid search
-- Ken VanDine <[email protected]> Wed, 26 Oct 2011 12:07:31 -0400
** Changed in: gwibber (Ubuntu Oneiric)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/864727
Title:
Gwibber failing to start, or starting very very slowly
To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/864727/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
