System log is spammed by non-existant interfaces

[jvalrog]

I don't exactly know if this is because the extension, but after my VPN is shut down, the logs show gnome-shell trying to access that device constantly.

Example:

sep 06 14:14:25 ubuntu gnome-shell[4160]: glibtop(c=4160): [WARNING] Failed to open "/sys/class/net/vpn/statistics/tx_packets": No such file or directory
sep 06 14:14:25 ubuntu gnome-shell[4160]: glibtop(c=4160): [WARNING] Failed to open "/sys/class/net/vpn/statistics/rx_bytes": No such file or directory
sep 06 14:14:25 ubuntu gnome-shell[4160]: glibtop(c=4160): [WARNING] Failed to open "/sys/class/net/vpn/statistics/tx_bytes": No such file or directory
sep 06 14:14:25 ubuntu gnome-shell[4160]: glibtop(c=4160): [WARNING] Failed to open "/sys/class/net/vpn/statistics/rx_errors": No such file or directory
sep 06 14:14:25 ubuntu gnome-shell[4160]: glibtop(c=4160): [WARNING] Failed to open "/sys/class/net/vpn/statistics/tx_errors": No such file or directory
sep 06 14:14:25 ubuntu gnome-shell[4160]: glibtop(c=4160): [WARNING] Failed to open "/sys/class/net/vpn/statistics/collisions": No such file or directory
sep 06 14:14:25 ubuntu gnome-shell[4160]: glibtop(c=4160): [WARNING] Failed to open "/sys/class/net/virtual0/statistics/rx_packets": No such file or directory
sep 06 14:14:25 ubuntu gnome-shell[4160]: glibtop(c=4160): [WARNING] Failed to open "/sys/class/net/virtual0/statistics/tx_packets": No such file or directory

Both vpn and virtual0 are temporary devices and it looks like they are not removed from the watch list of the extension once they are deleted??

[update] Can confirm it's the extension, once I disable it, the spam ends.

[fflewddur]

Thanks for reporting this! I think you're right, this seems like it's related to how TopHat is using libgtop, though I haven't been able to replicate it myself yet. Does the log spam occur roughly every two seconds?

[fflewddur]

I might have tracked this down, though I wasn't able to replicate it; can you let me know if this change resolves the issue for you?

[jvalrog]

I might have tracked this down, though I wasn't able to replicate it; can you let me know if this change resolves the issue for you?

I'll try later today, thanks