This bug was fixed in the package gwibber - 3.3.2-0ubuntu1
---------------
gwibber (3.3.2-0ubuntu1) precise; urgency=low
* New upstream release
- Drop the usage of threading.Thread and ensure the multiprocessing.Pool
is closed after the job is complete, this greatly reduces the system
load and stops the aggressive polling multiprocessing worker pools
used (LP: #906916)
- ported to libdee API changes
- ported to libunity API changes
* debian/gwibber-service.pyinstall, debian/gwibber-service.install
- Use a .pyinstall file to handle instaling stuff so we don't have to
copy custom.py
* debian/rules
- drop the copy of custom.py, it gets installed with .pyinstall file now
* debian/control
- bump build depends for libunity-dev and libdee-dev
- renamed build dep to gtkspell-3-dev
-- Ken VanDine <[email protected]> Fri, 13 Jan 2012 12:38:23 +0100
** Changed in: gwibber (Ubuntu)
Status: Triaged => 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/906916
Title:
gwibber-service has a child that polls at 10Hz which is causing a lot
of wakeup events
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/906916/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
