Version: unspecified (using KDE 4.7.2) OS: Linux my hardware sensors occasionally fail (maybe once every couple of minutes or so) and ksysguard interprets this as a value of zero and thus changes the displayed scale to have a minimum of zero. that means effectively that i can not use the feature of configuring a minimum value for the scale. Reproducible: Always Steps to Reproduce: 1) create a new tab 2) add some hardware temperature sensors as line graphs 3) set min/max for the scale (to a reasonable value greater than zero) 4) wait 5) occasionally a nonsensical value of zero will occur 6) the displayed scale will now have a min value of zero Actual Results: 7) the displayed min value will be zero until you close/restart ksysguard Expected Results: i _do_ like the fact that ksysguard automatically adjusts the displayed scale if values outside of the configured scale occur. so thanks for how step 6) works! however it would be nice if ksysguard would at some time return to the configured settings. like this: 7) wait some time until ksysguard forgets that there was a value of zero and then the displayed scale will again be as configured i assume that it is _normal_ that hardware sensors occasionally do not work. for example the following command will occasionally fail for me: root@white:/sys/devices/platform/applesmc.768# while true ; do for (( t=1 ; t < 11 ; ++t )) ; do echo -n "$(cat temp${t}_label)=$(cat temp${t}_input) " ; done ; echo "" ; done TB0T=31750 TC0D=64500 TC0P=57250 TM0P=58250 TN0P=54750 TTF0=54500 TW0P=70000 Th0H=57000 Th0S=57000 Th1H=56750 [...] TB0T=31750 TC0D=71500 TC0P=56750 TM0P=58250 TN0P=54250 TTF0=54500 TW0P=70000 Th0H=57500 Th0S=57250 Th1H=57250 TB0T=31750 TC0D=71500 TC0P=56750 TM0P=58250 TN0P=54250 cat: temp6_input: Input/output error If i am wrong in my assumption that it is normal that sensors fail occasionally then please ignore/close this bug! OS: Linux (x86_64) release 3.0.0-13-generic Compiler: gcc
For me the minimum value is ignored constantly. I can choose whatever I want, but the graph keeps starting at 0.
@DeMus. Even if you take something from Sensors Browser that is not an actual hardware sensor and certainly never 0? Like System/Processors or Memory/Physical Memory/Used Memory? If the Line Graphs for these start at 0 for you, then i guess you're experiencing a different bug, since I do not have this issue.
Subject problem still exists. Min and max limits for fixed graph range are ignored when read value doesn't fit the specified range. In this case range expands exceeding the specified limits to fit the read value. Taking into account such a bugs (not only with CPU) it messes graphs a lot: https://bugs.kde.org/show_bug.cgi?id=304145 Same issue, I think: https://bugs.kde.org/show_bug.cgi?id=302258
ksysguard is no longer maintained, in Plasma 6 there is the Plasma system monitor for this task. If your wish is still valid for the Plasma 6 replacement, please re-open and we can move this bug to the new product, thanks!