Comment 5 for bug 245197

Today I tested the newest version in proposed. The problem seems largely fixed, but not quite.

When I check the system load caused by gnome-system-monitor using the command "top" in the terminal, the CPU load is almost imperceptible. That's good.

But when I check the system load by double-clicking gnome-system-monitor, so that it opens it's own full-size window, I see the crazy values again (confirmed by top). 15 % CPU, with peaks as high as 21 %.

So it appears that as long as you use gnome-system-monitor only as a little meter in the panel, there's no problem with this new version. But do not double-click it, for then the trouble starts.

For most practical puposes the meter is therefore allright now. Upstream should deal with the remaining problem, though.