What has happened to the Network Interface sensors? They used to display the same way as the CPU sensors, with lines that went up & down with the data transfer signals. Now they slowly go up to some “maximum” level that they have registered and remain at that level indefinitely, an essentially static display which confers no useful information. Do everyone’s “System Monitor” displays do the same now, or just mine?
It’s looking fine for me. My “Memory and Swap History” is pretty flat, but the network history is having it ups and downs.
This is with 13.1 and KDE 4.11.5
Works fine here as well.
Maybe try to change some settings. (right-click on it and select “Properties”)
Well, I guess that answers one question for me - it still works for others.
Next question, how do I find out why mine doesn’t (work correctly)?
Hm. Have you tried to change the settings?
Create a new sheet (“File” menu) and add some Network sensors. Does it work then?
Could you maybe post a screen shot?
http://susepaste.org/63328206 - monitoring “Data” for both x-mit & rcv sensors
The displays have been this way since a bit over a week ago when about 32 or more updates came in at the same time. This is one of several ways the OS has been hosed ever since.
Notice this screenshot is of an added tab, which is the only kind of tab you can edit!
The original tab is unchangeable for the massive unwashed (us, me). There is no right-clickable option that I can find to change to the previous (wavy, such as in yours) display.
Tearing hair, here. As I said, more than just one problem here…
Hosed? Could you elaborate a bit please?
If you see other problems as well, this could of course be related.
As there has been a kernel update: have you tried to boot to the older kernel already to see if your problems a re gone then? (“Advanced Options”)
Notice this screenshot is of an added tab, which is the only kind of tab you can edit!
The original tab is unchangeable for the massive unwashed (us, me). There is no right-clickable option that I can find to change to the previous (wavy, such as in yours) display.
When you right-click on the display you should get at least one option “Properties” where you can configure scale, colors and so on.
Ha! Found the problem. It was, as usual, right between the chair and the keyboard.
“Hosed” = local colloquialism for “broke”, “busted”, “fubar”
http://onlineslangdictionary.com/meaning-definition-of/hosed
When I was checking and replacing the “Network History” sensors, I had never removed the “Data” sensors, which I had thought were the information sources for “Network History” but which seem to accumulate a “Total” figure, so when I tried adding the “Data Rate” sensors they displayed as nothing more than a line at the bottom of the “worksheet”. At the calibration level for “Data”, you could see no variation in “Data Rate”.
When I cleared out ALL the sensors and added in only the “Data Rate” for the “Receiver” and “Transmitter”, the “worksheet” promptly re-calibrated and gave me the display I had been looking for.
Silly me…
Bottom line; Start from an empty “worksheet” and only add in the “Data Rate” for the “Receiver” and “Transmitter” sensors.
There is still a problem in 13.1 (on this machine anyway) that caused me to get involved with this to start with; ksysguard sensors can only be added/removed/adjusted in a NEW tab. The original “hard-coded” tab accepts some adjustments, changes to colors, etc., but here. “Network History” shows no sensors at all, much less to adjust, and I see no way to add them in.
I suspect the newer versions, like 13.1, are using the newer ethernet connection names, like “enp3s0” in this case, while the “hard-coded” ksysguard “System Monitor” may still look for the older “Eth0” and can’t find it, hence no “Network History”.
Which is to say - this looks like it’s either still the same issue with ksysguard, or maybe it’s networkmanager?
so … as someone very famous once said … “When you see a fork in the road, take it!”
Any ideas, anyone? (without getting into whether this is opensuse or kde or “upstream”) is this “enp3s0” vs “Eth0” an issue for a bug report, and if so, let me know, please, and how to do it?
Thanks, Wolfi & Gogalthorp…
I usually delete “$HOME/.kde4” for each new release, and allow it to be recreated. Actually, I rename it, then move a small number of old files to the new version, where I want to keep the old data.
Perhaps that’s why I did not see any problem related to the device renaming.
Yeah, I know what “hosed” means.
I just wanted to know in more detail about the “several ways the OS has been hosed ever since”.
There is still a problem in 13.1 (on this machine anyway) that caused me to get involved with this to start with; ksysguard sensors can only be added/removed/adjusted in a NEW tab. The original “hard-coded” tab accepts some adjustments, changes to colors, etc., but here. “Network History” shows no sensors at all, much less to adjust, and I see no way to add them in.
That’s correct, and intended apparently.
But you can add as many custom sheets as you want, anyway.
I suspect the newer versions, like 13.1, are using the newer ethernet connection names, like “enp3s0” in this case, while the “hard-coded” ksysguard “System Monitor” may still look for the older “Eth0” and can’t find it, hence no “Network History”.
AFAICS without looking at the source code, it displays all network interfaces. If you choose “Properties” and click on the “Sensors” tab, you will see regexps like “network/interfaces/(!lo|bridge|usbus|bond).*/receiver/data”, which supposedly means to show all receiver/data/ sensors for all interfaces in network/interfaces, except those starting with “lo”, “bridge”, “usbus”, or “bond”.
And it does show “enp63s0” fine here:
http://wstaw.org/m/2014/03/08/ksysguard1_1.png
This is a fresh install though, so there was never an eth0 here.
On my other systems (that I upgraded), eth0 was kept as interface name (because it was set in /etc/udev/rules.d/70-persistent-net.rules), and it works there as well.
And I don’t see any mention of the interface name in the config file anyway.
If you manually added a sensor for a specific interface in a custom sheet, that one doesn’t work any more of course if the interface gets renamed.
But I don’t see any reason for a bug report at all there.
If the interface name is disturbing you (f.e. if you don’t want to recreate all your sheets) you can rename your interface back to “eth0” in YaST->Network Devices->Network Settings. You have to switch to “Traditional Method using ifup” to be able to do that, but the interface name should stick even when switching back to NetworkManager.