After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 590107 - Invalid maximal range for meters
Invalid maximal range for meters
Status: RESOLVED OBSOLETE
Product: system-monitor
Classification: Core
Component: general
git master
Other All
: Normal minor
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
: 625043 626738 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-07-29 05:59 UTC by Коренберг Марк
Modified: 2018-05-22 12:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Коренберг Марк 2009-07-29 05:59:20 UTC 
For example, for my Gigabit net, maximal range for network throughput should be always 1 Gigabit, if low-level link established as 1 Gbit, and 100 Mbit if link established as 100 mbit.

The same triaged for hard drive. My hard drive can read/write at speed about 70 MB/s. So graph should use this speed as maximal. If speed can't be discovered, there is two method - 1. user should specify maximal speed by hand, 2. maximal value during all history should be computed, saved and used.

Other information:
Comment 1 Коренберг Марк 2009-07-29 05:59:48 UTC 
Originals of this bug is: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/396015
Comment 2 Benoît Dejean 2009-07-31 12:30:23 UTC 
Hello Mark,

i won't change this back to the old behaviour, but one should be able to select a fixed scale.
Comment 3 Коренберг Марк 2009-07-31 19:11:34 UTC 
Totally agree with you. Scale should be selected (automatic or manual or fixed automatic ). And not only in system monitor but also in applet.
Comment 4 Robert Roth 2011-11-28 19:53:00 UTC 
*** Bug 625043 has been marked as a duplicate of this bug. ***
Comment 5 Robert Roth 2012-08-07 22:39:11 UTC 
*** Bug 626738 has been marked as a duplicate of this bug. ***
Comment 6 GNOME Infrastructure Team 2018-05-22 12:07:11 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-system-monitor/issues/26.