*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. add a monitor for cpu > core X > current cpu frequency (MHz) OBSERVED RESULT The graph is populated but the values are not updated at all EXPECTED RESULT The graph should upgrade at given interval SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.9.0-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: AB350-Gaming 3 ADDITIONAL INFORMATION Another software GtkStressTesting (downloaded from the aur) which uses lm_sensors shows the correct values for each core. The issue is present even booting a live version of Manjaro 24 (manjaro-kde-24.0-240513-linux69) or Kde neon (neon-user-20240520-1034). System was updated from plasma 5, manjaro-kde-23.1.4-240406-linux66 (plasma 5) booted live with the old ksysmonitor works as expected. It worked pre update. Before installing gtkstresstest i tried sensors-detect; this is the output. # sensors-detect version 3.6.0+git # System: Gigabyte Technology Co., Ltd. AB350-Gaming 3 [Default string] # Board: Gigabyte Technology Co., Ltd. AB350-Gaming 3-CF # Kernel: 6.9.0-1-MANJARO x86_64 # Processor: AMD Ryzen 5 1600 Six-Core Processor (23/1/1) This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): YES Silicon Integrated Systems SIS5595... No VIA VT82C686 Integrated Sensors... No VIA VT8231 Integrated Sensors... No AMD K8 thermal sensors... No AMD Family 10h thermal sensors... No AMD Family 11h thermal sensors... No AMD Family 12h and 14h thermal sensors... No AMD Family 15h thermal sensors... No AMD Family 16h thermal sensors... No AMD Family 17h thermal sensors... Success! (driver `k10temp') AMD Family 15h power sensors... No AMD Family 16h power sensors... No Hygon Family 18h thermal sensors... No AMD Family 19h thermal sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 thermal sensor... No VIA C7 thermal sensor... No VIA Nano thermal sensor... No Some Super I/O chips contain embedded sensors. We have to write to standard I/O ports to probe them. This is usually safe. Do you want to scan for Super I/O sensors? (YES/no): YES Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8686E Super IO Sensors' Success! (address 0xa40, driver `to-be-written') Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... Yes Found `ITE IT8792E Super IO Sensors' Success! (address 0xa60, driver `it87') Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): YES Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes Probing for `National Semiconductor LM78' at 0x290... No Probing for `National Semiconductor LM79' at 0x290... No Probing for `Winbond W83781D' at 0x290... No Probing for `Winbond W83782D' at 0x290... No Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): YES Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus Next adapter: AMDGPU DM i2c hw bus 0 (i2c-0) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 1 (i2c-1) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 2 (i2c-2) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 3 (i2c-3) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM i2c hw bus 4 (i2c-4) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM aux hw bus 0 (i2c-5) Do you want to scan it? (yes/NO/selectively): yes Next adapter: AMDGPU DM aux hw bus 1 (i2c-6) Do you want to scan it? (yes/NO/selectively): yes Client found at address 0x4a Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Analog Devices ADT7410/ADT7420'... No Probing for `Analog Devices ADT7411'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP435'... No Probing for `National Semiconductor LM73'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Client found at address 0x4b Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Analog Devices ADT7410/ADT7420'... No Probing for `Analog Devices ADT7411'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP435'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `NXP/Philips SA56004'... No Probing for `Analog Devices ADT7481'... No Next adapter: AMDGPU DM aux hw bus 2 (i2c-7) Do you want to scan it? (yes/NO/selectively): yes Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `it87': * ISA bus, address 0xa60 Chip `ITE IT8792E Super IO Sensors' (confidence: 9) Driver `k10temp' (autoloaded): * Chip `AMD Family 17h thermal sensors' (confidence: 9) Driver `to-be-written': * ISA bus, address 0xa40 Chip `ITE IT8686E Super IO Sensors' (confidence: 9) Note: there is no driver for ITE IT8686E Super IO Sensors yet. Check https://hwmon.wiki.kernel.org/device_support_status for updates. Do you want to generate /etc/conf.d/lm_sensors? (YES/no): YES Created symlink /etc/systemd/system/multi-user.target.wants/lm_sensors.service → /usr/lib/systemd/system/lm_sensors.service.
Do other sensors work correctly? E.g. CPU or Memory usage?
(In reply to Arjen Hiemstra from comment #1) > Do other sensors work correctly? E.g. CPU or Memory usage? Yes they do, on my custom page I have a little of everything: cpu use %, gpu use/clock/temp/ram, ram usage, disk r/w speeds, ethernet speed, they all work. Plasma-systemmonitor is now version 6.0.5 because manjaro pushed an update, the issue is still there.
Just to be clearer when I say the values are not updated after the graph is popupated I mean the graph is created (let's say a bar graph) with the 12 threads, each bar is assigned a color and a value that is valid (right now lowest is 2.9GHz, highest is 3.4GHz) but the values are not updated in real time or ever.
Manjaro got updated, issue persists. Plasma-systemmonitor is 6.0.5 Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-3-MANJARO (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 1600 Six-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: AB350-Gaming 3
Update: after a lot of searching I found a 6 years old reddit thread in which someone suggested to enable AMD cool & quiet because otherwise cpupower won't load drivers. It worked before with it disabled, I don't know why. So I don't think the issue is with plasma-system monitor anymore.