This bug was filed months ago and with precise coming, is no longer
applicable.
** Changed in: gwibber (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/876500
Title:
Updating your status in gwibber causes gwibber and Xorg to take 100%
cpu
Status in “gwibber” package in Ubuntu:
Invalid
Bug description:
When you update your status in gwibber, it slams CPU resources (likely
due to the "pretty" overlay). It literally takes 100% cpu until you
close that update status overlay. In the status window you type and
then wait for the letters to appear (think 2400 baud modem days), it's
just not usable.
This is with 3.2.0.1 (oneiric) running on an i7 w/ 8gb of ram.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/876500/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
