Summary: | USB sensor devices name changes causes sensors not to be found on nearly every boot | ||
---|---|---|---|
Product: | [Frameworks and Libraries] ksystemstats | Reporter: | Ville Aakko <ville.aakko> |
Component: | General | Assignee: | KSysGuard Developers <ksysguard-bugs> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | ahiemstra, kde, nate, plasma-bugs, postix |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | A screenshot demonstrating the issue and cause |
Description
Ville Aakko
2023-02-23 00:39:27 UTC
Created attachment 156627 [details]
A screenshot demonstrating the issue and cause
> does it use libsensors?)
Yes. I don't know what we can do here tbh the name itself is not very useful, it's not unique as far as I know.
For your use case you can use a hidden feature, you can configure sensors with regex. For example the default overview page does
highPrioritySensorIds=["network/(?!all).*/download","network/(?!all).*/upload"]
You should find your page config ~/.local/share/plasma-systemmonitor, locate the sensor ids there and edit so it matches,in your case something like
"lmsensors/corsaircpro.*/temp1"
and so on
Hi David! Wow, I didn't know there is such a nice workaround / hidden feature! As a workaround, I've been running an in-place sed -command via my crontab @reboot (on the files you've mentioned). But I think this feature is more cleaner, though the sed works, too ;-). Cheers! |