In 15.1 I could select udisks sources to monitor SSD’s and HDD’s temperatures.
In 15.2 I still have udisks sources but only the HDD sources work. SSD’s (either SATA or NVME) return “OFF”.
In 15.3 there are no udisks sources, only the usual lmsensors (k10temp). And after boot or logout/login, CPU temp is only shown if I reload the sources. NVidia temp is the only sensor that works as it should (nvidia-smi).
Below a list of the sensor* and udisk* packages installed in 15.3. LEAP 15.2 has the same packages, minus version numbers of course.
:~> zypper se -i sensor
Carregando dados do repositório...
Lendo os pacotes instalados...
S | Name | Summary | Type
--+------------------------+------------------------------------------+-------
i | libQt5Sensors5 | Qt 5 Sensors library | pacote
i | libQt5Sensors5-imports | QML imports for the Qt 5 Sensors library | pacote
i | libsensors4 | Hardware health monitoring library | pacote
i | sensors | Hardware health monitoring for Linux | pacote
:~> zypper se -i udisk
Carregando dados do repositório...
Lendo os pacotes instalados...
S | Name | Summary | Type
--+--------------------+----------------------------------------------+-------
i | libudisks2-0 | Dynamic library to access the UDisksd daemon | pacote
i | libudisks2-0_btrfs | UDisks module for btrfs | pacote
i | udisks2 | Disk Manager | pacote
i | udisks2-lang | Translations for package udisks2 | pacote
:~>
The is a version of thermal monitor in KDE’s Add New Plasma Widgets download dialog that supposedy fix the need to reload the CPU source after boot/login, but it didn’t work for me, it actually stopped showing some sources.
I don’t have a clue on how to improve this. Any ideas?
There are reports in Arch Linux with the inverse behavior, i.e., lost CPU/lm sensors but not udisks. It seems this happens with Plasma 5.20+. According to KInfocenter my LEAP 15.3 system uses Plasma 5.18.6.
ksysguard and ksysguardd are installed, provided by ksysguard5 5.18.5-bp153.1.30. There’s the small difference between plasma versions - 5.18.6 and 5.18.5 - but that’s probably not relevant, as all plasma packages come from the main & update repos.
Yes, but no change from the output as shown in post #2 above, i.e., no udisks readings, supposing they should appear there.
In 15.2 only nvme temp reading are shown in the output. There is also an HDD and a SSD in that machine that are not listed in the output, but can be shown with the thermal monitor widget.
Now that is something I’m confused about, as these repos where not part of the original installation, and only got pulled in when I tried to install something I don’t recall now, not from the standard repos. There are repos for SLE SP1, 2 &3, with :GA and :Update extensions, and some error out when updating, so I disabled them in YAST. But this is OT, I’ll post another thread if I can’t understand this.
Here I go OT again, but just for clarification. From https://forums.opensuse.org/showthread.php/554462-zypper-dup-invalid-repositories?p=3032915#post3032915 (thanks malcomlewis!) these repos are wrong, something to do with wrong 1-click installs. If I add only the package repo in Yast, it installs OK, but every time I use 1-click install it adds the repos that error out, so the package is not installed, and I have do disable/delete them every time in Yast.
Is there any way to block these repos for ever, or at least till the end of the world?