This bug was fixed in the package libindicator -
12.10.2+14.04.20140304-0ubuntu1
---------------
libindicator (12.10.2+14.04.20140304-0ubuntu1) trusty; urgency=low
[ Marco Trevisan (Treviño) ]
* IndicatorImageHelper: always try to use a GIcon or the filename as
source of the GdkImage We don't need to fallback to pure pixbuf,
unless an indicator provided a custom icon that is not in the
current theme path. This helps a lot in reducing the Unity7 workload
as this decreases the cases where we need to encode the pixbuf
contents, send them via dbus to unity, encode them back, reload to a
new pixbuf... Also thanks to this, the library clients can load the
actual icon, scaled at the value they want. (LP: #784055)
-- Ubuntu daily release <[email protected]> Tue, 04 Mar 2014
10:58:35 +0000
** Changed in: libindicator (Ubuntu)
Status: New => 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/784055
Title:
compiz CPU usage increases dramatically when running indicator-
multiload
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-multiload/+bug/784055/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
