Description: ACPI thermal_zone0 (CPU temperature) fails to refresh, just displays initial value. Overview: ACPI thermal_zone0 (CPU temperature) fails to refresh, stays at value first reported. This value is correct as far as I can determine. Rebooting displays increased temperature as expected. Steps to Reproduce: Start Xfce and observe the value displayed on the panel. Actual Results: Value fails to change. The displayed value is checked against: /usr/bin/vcgencmd measure_temp Expected Results: I expect the value to track $(/usr/bin/vcgencmd measure_temp) Build Date & Hardware: dmesg: [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.14.34-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1110 SMP Mon Apr 16 15:18:51 B ST 2018 [ 0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d ... [ 0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Rev 1.2 cat /etc/issue: Raspbian GNU/Linux 9 \n \l All software is current per: sudo apt-get update && sudo apt-get dist-upgrade -y Additional Information: I'm enjoying Xfce on my raspberry pi. CPU temperature is a bit of a worry so I'm looking forward to getting this working...
I don't know of vcgencmd. the ACPI values are read from /proc/acpi/ibm/thermal and/or /sys/bus/acpi/drivers/thermal/LNXTHERM\:00/thermal_zone/temp. You could compare to these values, rather. Apart from that, the update interval in the sensors plugin can be adjusted. Try setting 10 seconds for example and see whether the values change. When you installed the plugin on your own, beware the output and hints from ./configure, where you can choose between /proc and /sys. Your distribution's maintainer might have already taken an unsuitable choice for you, in case you installed the preconfigured package from your distribution.