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
Thermal shows NaN since the last update #520
Comments
Same here (Ubuntu 18.04 4.18.0-18-generic) regardless of chosen sensor. |
It seems like my Ubuntu 18.04 system has the same issue, but not my Ubuntu 19.04 one. The Frequency stat seems to have a similar issue on Ubuntu 18.04. |
Also seeing NaN in thermals now — regardless of sensor selected. |
Also Fan and Frequency show NaN |
I've confirmed this as well. It looks like the value returned |
When I log the value, it appears in syslog as "36000#012", and when I use I don't have much experience reading the temperature sensor, as I've never had to. Is that a valid value, possibly meaning my computer doesn't have that sensor and just returns some absurdly high default value? |
Nevermind. It looks like this commit is what broke it. I've reverted the use of ByteArray.toString, which has fixed it for me. |
@shemgp Do you know why ByteArray doesn't work here? |
After I checked out the latest commit, the thermal temperature and fan frequency is fixed for me. However the CPU frequency is still broken showing |
Same here: freq, temp and fan speed are NaN |
same here |
Finally had time to debug this: In gnome-shell 3.28, when you pass While for newer gnome-shells (I tested, 3.32), So maybe we can have a work around like these? total_frequency += parseInt(ByteArray.toString(as_r[1])); TO let value = as_r[1];
if (!ByteArray.toString(value).match(/GjsModule byteArray/))
value = ByteArray.toString(value);
total_frequency += parseInt(value); |
Are there plans to update the version in ubuntu software center with this fix? I have the latest version installed from there and am seeing this issue. Thx! |
Just to note, I observed the issue with the extension update on OpenSUSE Leap 15.0 (Gnome 3.26.2), but it works just fine with an up to date OpenSUSE Tumbleweed (Gnome 3.32.2). |
I tried the mentioned solutions of both @shemgp and @chrisspen on Ubuntu 18.04.1 LTS with gnome-shell version 3.28.3 but It didn't work |
It has been fixed after I rebooted my machine. (it didn't fix by reloading the plugin) Thanks @shemgp and @chrisspen |
Building up on @ibrahimalkurdi 's answer, here's explicitly what you should do:
to
to
to
|
Your solution worked perfectly on my Ubuntu 18.04 LTS. I installed gnome-shell-extension-system-monitor from the Ubuntu Software Center and I had the NaN problem. |
… on Ubuntu 18.04 add backward support for Gnome 3.28 , fix NaN temperature and disk IO on Ubuntu 18.04 . related issues: paradoxxxzero#520 paradoxxxzero#526 paradoxxxzero#594 paradoxxxzero#597 paradoxxxzero#601 thankjura/ds4battery#4 I don't have dedicated GPU to test paradoxxxzero#592 but it should be possible to fix in the same way. inspired by @shemgp and @EBoisseauSierra
Resolved in #777 |
Yesterday, I've got an update for this extension. Today, I've noticed that the thermals are only showing NaN (not a number) in the extension. Psensor displays it correctly.
I'm using Ubuntu 18.04 64-bit with kernel 4.15.0-48-generic on an Intel Core i3-2100.
The text was updated successfully, but these errors were encountered: