Bug 429159

Can you please attach a screenshot?

Created attachment 133389 [details]
Screenshot

Sure.

Thanks.

This happens because the sensors you are using do not have a maximum value, so they have no way of knowing what they need to scale to. I actually do not know if lm_sensors even reports this. We are working on some new sensor setup that should fix this for certain sensors but others will still have this issue, since the data is either not available or there simply is no known proper maximum.

I see. FWIW below is my sensors output and there is only one reasonable "max" entry.
I guess the sanest/easiest approach would be to enable the data range option (like in line chart) and have the user configure the ranges.

$ sensors
nct6797-isa-0a20
Adapter: ISA adapter
Vcore:         1.22 V  (min =  +0.00 V, max =  +1.74 V)
in1:           1.01 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:           3.39 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:           3.38 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:           1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:         144.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:         832.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:           3.39 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:           3.20 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:           1.85 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:        824.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:          1.15 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:        680.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:          1.53 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
FAN_CPU:        0 RPM  (min =    0 RPM)
FAN_IN:       463 RPM  (min =    0 RPM)
FAN_OUT:      453 RPM  (min =    0 RPM)
CS:           +32.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = CPU diode
CPU:          +36.0°C  (high = +115.0°C, hyst = +90.0°C)  sensor = thermistor
AUXTIN0:      +35.0°C  (high = +115.0°C, hyst = +90.0°C)  sensor = thermistor
AUXTIN2:      +35.5°C    sensor = thermistor
beep_enable: disabled

k10temp-pci-00c3
Adapter: PCI adapter
Vcore:         1.41 V  
Vsoc:          1.13 V  
Tctl:         +37.6°C  
Tdie:         +37.6°C  
Icore:        36.00 A  
Isoc:         10.25 A  

nvme-pci-2500
Adapter: PCI adapter
Composite:    +39.9°C  (low  = -273.1°C, high = +69.8°C)
                       (crit = +79.8°C)

amdgpu-pci-2600
Adapter: PCI adapter
vddgfx:      900.00 mV 
FAN_GPU:      616 RPM  (min = 1000 RPM, max = 4200 RPM)
GPU:          +34.0°C  (crit = +89.0°C, hyst = -273.1°C)
power1:       16.22 W  (cap = 150.00 W)

nvme-pci-0100
Adapter: PCI adapter
SSD:          +28.9°C  (low  = -273.1°C, high = +76.8°C)
                       (crit = +78.8°C)
Sensor 1:     +28.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +36.9°C  (low  = -273.1°C, high = +65261.8°C)

Google has brought me here... I see the same and can confirm. My sensors have high and critical but no max, so I understand the conundrum. 

"We are working on some new sensor setup that should fix this for certain sensors"

For what it's worth *pie chart* allows for a manual data range. Could be a great addition to horizontal bars: let the user fix it!

Horizontal bars in 6.4 supports editing the range used for the sensors. Since lm_sensors does not provide the information required for automatic data ranges, that's the best way to solve this.