Linking to correct upstream bug (which I just reported because I
couldn't find an existing one):
http://bugzilla.gnome.org/show_bug.cgi?id=524830. In sum: g-s-m uses too
much CPU. It is not just a matter of false reporting (like I had
previously incorrectly suggested), and is not related to the new
Resources graphs introduced in 2.22.
** Changed in: gnome-system-monitor (Debian)
Bugwatch: Debian Bug tracker #471152 => GNOME Bug Tracker #524830
Status: Confirmed => Unknown
** Changed in: gnome-system-monitor (Debian)
Importance: Unknown => Undecided
Bugwatch: GNOME Bug Tracker #524830 => None
Status: Unknown => New
** Changed in: gnome-system-monitor
Importance: Undecided => Unknown
Bugwatch: None => GNOME Bug Tracker #524830
Status: New => Unknown
--
Excessive CPU usage by Gnome System Monitor
https://bugs.launchpad.net/bugs/93847
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
