System Monitor's network history graph always starts at zero

Bug #432184 reported by Mike.lifeguard on 2009-09-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gnome System Monitor
Fix Released
gnome-system-monitor (Ubuntu)

Bug Description

Binary package hint: gnome-system-monitor

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.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-system-monitor
Package: gnome-system-monitor
 PATH=(custom, no user)
SourcePackage: gnome-system-monitor
Uname: Linux 2.6.30-020630-generic i686

Mike.lifeguard (mikelifeguard) wrote :
Pedro Villavicencio (pedro) wrote :

do you get the same on karmic? any proposed solution for it?

Changed in gnome-system-monitor (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Incomplete
Mike.lifeguard (mikelifeguard) wrote :

Yep, same on Karmic.

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.

Mike.lifeguard (mikelifeguard) wrote :

Or alternatively, just get your data when you want to start graphing (instead of the other way around)

Pedro Villavicencio (pedro) wrote :

This bug is an upstream one and it would be quite helpful if somebody experiencing it could send the bug the to the people writing the software. You can learn more about how to do this for various upstreams at . Thanks in advance!

Changed in gnome-system-monitor (Ubuntu):
importance: Low → Wishlist
status: Incomplete → New
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:

Changed in gnome-system-monitor (Ubuntu):
importance: Wishlist → Low
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
status: New → Triaged
Changed in gnome-system-monitor:
status: Unknown → New
Changed in gnome-system-monitor:
importance: Unknown → Medium
Changed in gnome-system-monitor:
status: New → Confirmed
Robert Roth (evfool) on 2011-11-27
Changed in gnome-system-monitor (Ubuntu):
assignee: nobody → Robert Roth (evfool)
status: Triaged → In Progress
Changed in gnome-system-monitor:
status: Confirmed → In Progress
Robert Roth (evfool) on 2012-07-27
Changed in gnome-system-monitor (Ubuntu):
status: In Progress → Triaged
assignee: Robert Roth (evfool) → nobody
Changed in gnome-system-monitor:
status: In Progress → Fix Released
Changed in gnome-system-monitor (Ubuntu):
status: Triaged → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-system-monitor -

gnome-system-monitor ( trusty; urgency=low

  * Backport some upstream changes
  * debian/patches/git_segfault_fix.patch
    - "Fix segfault on view mode change with process properties open."
      (lp: #1246813)
  * debian/patches/git_grid_rendering.patch:
    - "display without grid" (lp: #1093582)
  * debian/patches/git_chart_value.patch:
    - starts charts with the correct value instead of 0 (lp: #432184)
 -- Sebastien Bacher <email address hidden> Tue, 05 Nov 2013 16:03:26 +0100

Changed in gnome-system-monitor (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.