-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No such file or directory for file '/sys/class/hwmon/hwmon0/temp1_input' #135
Comments
Seems to be a pstutil bug, could you please share your version of pstuil? |
Alright
|
Could you please list the content of the directory |
|
Same here on openSUSE Tumbleweed, kernel 5.3.1.
|
@bubbleguuum, so these error did not appear before the update? There are quite a lot of issues with hwmon in Linux. As an example: giampaolo/psutil#1323 These warnings are displayed each time |
Oh, indeed.
I see a lot of them on startup and no pattern when the occur again. But it is way less then every update cycle. |
I'm confirming that these errors do not happen on Kernel 5.2 (tried 5.2.14) |
Also the same here.
I misunderstood the function of |
same error for me on Manjaro 18.1.3 with 0.8.3 version of s-tui |
Since this is probably reproducible on certain kernel version, and requires installation of hardware (no temperature sensors in VM) it will take me some time to address this. Any help is appreciated. |
Ok, dusted out an X220 with Majaro (thanks @liberodark), install kernel 5.3 and was able to reproduce the bug. It appears that starting 5.3 kernel version, there is a file for (for example) Interestingly, there is sometimes As smartly stated by @giampaolo, Linux's The immediate action is to ignore the warning emitted by @bubbleguuum @jiblime @liberodark @BjoernDaase, please confirm fix in latest master |
Confirming issue is fixed in master |
Fixed in version 1.0 |
Step 1: Describe your environment
Step 2: Describe the problem:
Observed Results:
Those get spammed onto the console, disrupting the graphs shown:
Debug Results, output of
s-tui -d
created in a file_s-tui.log
:Step 3: Reproduce the problem:
Steps to reproduce:
s-tui
The text was updated successfully, but these errors were encountered: