GNOME Bugzilla – Bug 626846
System Monitor's network history graph always starts at zero
Last modified: 2013-04-27 21:55:42 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/432184 "The network history graph always begins at zero KB/s, then increases to the current value, then tracks that value through time. Compare this to memory and CPU, which both start at the current value then track it. Please ensure the graph shows the current value as soon as it starts being drawn, rather than beginning at zero." "I guess the software must start with a value of zero which then gets replaced by real data - but that zero gets graphed. So don't start graphing until you have a real data point." "Or alternatively, just get your data when you want to start graphing (instead of the other way around)"
Created attachment 202258 [details] [review] Proposed patch The attached patch implements the first suggestion of the reporter, so only starts displaying the network graph when we have some real data, which means one second later than the other graphs, because at startup we only have the total bytes sent/received, and we have to wait one second to calculate the current bytes/second.
[Adding missing "QA Contact" entry so system monitor bug report changes can still be watched via the "Users to watch" list on https://bugzilla.gnome.org/userprefs.cgi?tab=email when the assignee is changed to an individual.]
Created attachment 220028 [details] [review] Proposed patch updated Updated patch to be able to apply it on the current master.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.