Package: gnome-power-manager Version: 3.4.0-2 This is related to, but ultimately a separate problem from the one detailed in bug 689298. When gnome-power-statistics is run on a Linux system without CONFIG_TIMER_STATS=y set in the kernel, upowerd won't work correctly, and indeed behaves horribly, which impacts gnome-power-statistics in a negative manner. In that circumstance, gnome-power-statistics will leak memory rapidly and without bounds while it consumes substantial CPU resources. The memory leak is arguably the bigger problem, but suffice it to say that even if upowerd is broken and not responding correctly there's no good reason for gnome-power-statistics to consume memory endlessly.
-- Jamie Heilman http://audible.transient.net/~jamie/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org