Skip to content
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

org.mate.panel.applet.NetspeedAppletFactory an unstoppable log in /var/log/syslog when is missing the usb net device #670

Open
aprilsettember opened this issue Sep 1, 2024 · 1 comment

Comments

@aprilsettember
Copy link

Expected behaviour

I would like this error log to end after a few cycles, or to reduce its reproduction a lot, I don't always use the laptop with the internet key inserted and I don't have a wifi network available, it's difficult to even read the normal syslog since it is constantly changing/updating.

Actual behaviour

linux-user-80ec org.mate.panel.applet.NetspeedAppletFactory[5461]: glibtop(c=5461): [WARNING] Failed to open "/sys/class/net/usb0/statistics/tx_errors": File or directory does not exist (This log is continuous and unstoppable when the USB net key is not insertedand /var/log/syslog grows rapidly.)

Steps to reproduce the behaviour

Just have the laptop without the usual internet key inserted and do not have an alternative wifi network available, open the syslog log with a linux log viewer.

MATE general version

Mate 1.26.0

Package version

mate-applets 1.26.1-1

Linux Distribution

Debian 12.6 in Italian

Link to bugreport of your Distribution (requirement)

https://www.debian.org/Bugs/

@lukefromdc
Copy link
Member

For a potential workaround try opening the applet's preferences dialog and setting "Network Device" to anything else. Fixing this in the code would basically require checking that the device was valid before doing anything with it. I don't know if a removed device disappears from the list entirely.

The error log itself is presumably being controlled by the applet itself misbehaving, it's not the fault of the logging system that we don't even control.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants