System monitor widgets not showing any sensors

As I mentioned in the title, the newly installed KDE desktop, when using widgets such as CPU usage, or memory usage, they do not show anything, it's like they cannot detect any sensors whatsoever. Does anyone have an idea what might be the issue? I have lm_sensors installed

System:    Kernel: 5.10.28-1-lts x86_64 bits: 64 compiler: gcc v: 10.2.0 
           parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts root=UUID=8ed53bac-aff7-4011-a9e8-ccb8fb2376b8 rw 
           [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 
           systemd.unified_cgroup_hierarchy=1 loglevel=3 
           Desktop: KDE Plasma 5.21.4 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux 
Machine:   Type: Desktop System: Gigabyte product: B450M DS3H v: N/A serial: <filter> 
           Mobo: Gigabyte model: B450M DS3H-CF v: x.x serial: <filter> UEFI: American Megatrends v: F51 date: 07/29/2020 
CPU:       Info: 8-Core model: AMD Ryzen 7 1700 bits: 64 type: MT MCP arch: Zen family: 17 (23) model-id: 1 stepping: 1 
           microcode: 8001138 cache: L2: 4 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 95805 
           Speed: 2556 MHz min/max: 1550/3000 MHz boost: enabled Core speeds (MHz): 1: 2556 2: 2971 3: 2632 4: 2758 5: 2561 
           6: 2580 7: 3154 8: 2944 9: 2558 10: 2555 11: 2566 12: 2845 13: 2945 14: 2571 15: 2558 16: 3014 
           Vulnerabilities: Type: itlb_multihit status: Not affected 
           Type: l1tf status: Not affected 
           Type: mds status: Not affected 
           Type: meltdown status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA GP102 [GeForce GTX 1080 Ti] vendor: eVga.com. driver: nvidia v: 460.67 
           alternate: nouveau,nvidia_drm bus-ID: 07:00.0 chip-ID: 10de:1b06 class-ID: 0300 
           Display: x11 server: X.org 1.20.10 compositor: kwin_x11 driver: loaded: nvidia resolution: <missing: xdpyinfo> 
           OpenGL: renderer: GeForce GTX 1080 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 460.67 direct render: Yes 
Audio:     Device-1: NVIDIA GP102 HDMI Audio vendor: eVga.com. driver: snd_hda_intel v: kernel bus-ID: 07:00.1 
           chip-ID: 10de:10ef class-ID: 0403 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel 
           bus-ID: 09:00.3 chip-ID: 1022:1457 class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.28-1-lts running: yes 
           Sound Server-2: JACK v: 0.125.0 running: no 
           Sound Server-3: PulseAudio v: 14.2 running: yes 
           Sound Server-4: PipeWire v: 0.3.25 running: no 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169 v: kernel 
           port: f000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200 
           IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Bluetooth: Device-1: ASUSTek Broadcom BCM20702A0 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-9:3 chip-ID: 0b05:17cb 
           class-ID: fe01 serial: <filter> 
           Report: This feature requires one of these tools: hciconfig/bt-adapter 
Drives:    Local Storage: total: 2.73 TiB used: 9.17 GiB (0.3%) 
           SMART Message: Required tool smartctl not installed. Check --recommends 
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 250GB size: 232.89 GiB block-size: 
           physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: 1B2QEXE7 temp: 41.9 C 
           scheme: GPT 
           ID-2: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000DM003-1CH162 size: 931.51 GiB block-size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC47 scheme: MBR 
           ID-3: /dev/sdb maj-min: 8:16 vendor: Kingston model: SKC600512G size: 476.94 GiB block-size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: <filter> rev: 0104 scheme: GPT 
           ID-4: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB block-size: 
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: CC43 scheme: GPT 
           ID-5: /dev/sdd maj-min: 8:48 vendor: Kingston model: SUV500240G size: 223.57 GiB block-size: physical: 4096 B 
           logical: 512 B speed: 6.0 Gb/s rotation: SSD serial: <filter> rev: 56RI scheme: GPT 
Partition: ID-1: / raw-size: 232.63 GiB size: 232.63 GiB (100.00%) used: 9.17 GiB (3.9%) fs: btrfs dev: /dev/nvme0n1p2 
           maj-min: 259:2 
           ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 546 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 
           maj-min: 259:1 
           ID-3: /home raw-size: 232.63 GiB size: 232.63 GiB (100.00%) used: 9.17 GiB (3.9%) fs: btrfs dev: /dev/nvme0n1p2 
           maj-min: 259:2 
           ID-4: /var/log raw-size: 232.63 GiB size: 232.63 GiB (100.00%) used: 9.17 GiB (3.9%) fs: btrfs dev: /dev/nvme0n1p2 
           maj-min: 259:2 
           ID-5: /var/tmp raw-size: 232.63 GiB size: 232.63 GiB (100.00%) used: 9.17 GiB (3.9%) fs: btrfs dev: /dev/nvme0n1p2 
           maj-min: 259:2 
Swap:      Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100) 
           ID-1: swap-1 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0 
           ID-2: swap-2 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1 
           ID-3: swap-3 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2 
           ID-4: swap-4 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3 
           ID-5: swap-5 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram4 
           ID-6: swap-6 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram5 
           ID-7: swap-7 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram6 
           ID-8: swap-8 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram7 
           ID-9: swap-9 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram8 
           ID-10: swap-10 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram9 
           ID-11: swap-11 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram10 
           ID-12: swap-12 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram11 
           ID-13: swap-13 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram12 
           ID-14: swap-14 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram13 
           ID-15: swap-15 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram14 
           ID-16: swap-16 type: zram size: 1.96 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram15 
Sensors:   System Temperatures: cpu: 47.0 C mobo: N/A gpu: nvidia temp: 61 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 27% 
Info:      Processes: 357 Uptime: 37m wakeups: 0 Memory: 31.37 GiB used: 4.75 GiB (15.1%) Init: systemd v: 248 tool: systemctl 
           Compilers: gcc: 10.2.0 Packages: pacman: 880 lib: 237 Shell: Zsh v: 5.8 running-in: yakuake inxi: 3.3.03 


Install , opps, you do

sudo pacman -Syu lm_sensors

after use

sudo sensors-detect

but do you run this ^

3 Likes

Thanks for the tip, i assumed that this was something i needed to do, but i was also required to run:

kquitapp5 plasmashell && kstart5 plasmashell

in order to get sensors detected. And i know there is a faster way to do this, but i have an alias for this command :smiley:

Thanks again!

4 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.