-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
RuntimeWarning: ignoring OSError... #1203
Comments
@giampaolo any idea where this PsUtil warning message came from ? |
Some more information. Looking at the file referenced in the error above
the first psutil issue quoted (1009) has a comment about disabled wireless devices. The laptop I'm running glances on is usually connected via an ethernet cable, not wifi. When I enable the wireless device the error messages disappear. My original comments about this error appearing due to an upgrade were a misunderstanding on my part. These errors occur when the wifi is disabled, which is still an issue I think. Hardware: HP 250 G5 Notebook Intel Core i5-6200U, Intel Wireless 3165 driver: iwlwifi. |
Looks like it comes from |
@netlexer can you try to run Glances with the --disable-sensors option and tell us if the error message is stil displayed ? |
With the --disable-sensors option the error message is still displayed, but only once, before the main glances screen is displayed; i.e. it doesn't repeat like before. |
I was getting the same and can confirm that --disable-sensors stops the error traceback.. but now the sensor displays aren't working (of course) |
i have same problem on arch manjaro python3.6 requests 2.18.4 has requirement urllib3<1.23,>=1.21.1, but you have urllib3 1.18.1. |
Same problem on Debian unstable, and confirmed it looks related to wifi sensor: when wifi is not disabled everything is fine. Thanks |
+1 here on Fedora 27 Linux 4.15.3. When I disable wifi, I get this error, if I re-enable it, the error is resolved. Hope that helps. |
Same here, on a laptop with Arch and kernel 4.15.3 same error (and same workaround) happens. On a desktop computer with the same distro and kernel don't. So it seems something related to laptops. Enabling and disabling wifi on laptop doesn't help here. |
I'm seeing the same issue after upgrading to Fedora 28 with glances-2.11.1-2.fc28.noarch and python-psutil-5.4.3-4.fc28.src.rpm WiFi is disabled in BIOS in my case |
Same here on Glances v2.11.1 with psutil v5.4.5 Error messages look like this For every |
Just to push this, I have the same issue after a fresh install of Fedora 28 (all updates to day installed) with |
This is also happening on Ubuntu 18.04 LTS.
|
I'd like to add that I'm having the same issue on Arch Linux (4.17.3-1-ARCH) with The issue appears to be caused by a temperature sensor on my discrete AMD GPU, which doesn't provide a temperature if it is switched off (which it is most of the time, since I'm primarily using my integrated Intel GPU). This causes the In that aspect, it is pretty much the same issue as the one with the disabled Wifi mentioned before, running glances with sensors disabled resolves the errors continuously being printed on the screen. Might there be a way to display @adocampo since you're also having this issue on a laptop and not on a desktop (which doesn't use hybrid graphics), might the issue in your case also be caused by a reading from the discrete GPU sensor? |
@CvBeijsterveldt Hello, i just push a patch on the DEVELOP branch. Can you test it on your system ? |
Just checked out the develop branch and installed |
I can confirm that |
I have a similar problem on Mint 19 Cinnamon, and 'Glances v2.11.1 with psutil v5.4.2', when there is no network. For I see this before the program starts and subsequently the program's display is messed up:
|
Also happens on Ubuntu 18.04 I would advise recommending to the user to use |
After the last glances package update on an up to date Arch linux system, glances now outputs the following lines to standard error:
These lines are repeated during the program run, messing up the display. Redirecting the output
solves the immediate display problem, though this is obviously not ideal.
As stated, this has only started happening after glances was upgraded (2.11.1-1 -> 2.11.1-2) a few days ago. No change to the installed version of python-psutil occurred during this time.
The text was updated successfully, but these errors were encountered: