I am thinking about posting a bug-report (minor) but somehow annoying bug I do notice but i would like to know if anybody else experience the same.
When you click on the networkmanager applet and select a specific interface (like a vpn you connected to) the infos about this connection (time, amount of data transferred etc) are all not available.
This is true for openVPN connections but is also true for e.g. eth or wlan (which do not show amount of data transmitted and are “flatliners” in the graphic. Also the time of connection is always about: 1 minute, and then resets.
Thank you for letting me know if you have the same, so I will then report the cosmetic bug.
Is that in all (supported) levels of openSUSE. And on all Desktop Environments?
FWIW cannot confirm your status on 64bit os
this laptop shows the following
Type: Wireless 802.11
Connection State: Connected
IP Address: 192.168.1.100
Connection Speed: 1 MBit/s
System Name: wlan0
MAC Address: 20:16:D8:xx:xx:xx
Driver: ath9k
Access Point (SSID): 3MobileWiFi-xxxx
Access Point (MAC): 0C:37:DC:xx:xx:xx
Band: b/g
Channel: 1 (2412 MHz)
Rx: 2.31 MB
TX: 881.84 KB
its assumed you’ve tried a re-install of all nw packages
I will second the observation: for me Wired and Wireless connects work as intended on HPDV7T, 12.2/KDE 4.9
Comment: In the distant past (11.x vintage) I had a similar issue. Solution was to search out updated specific drivers for my networking devices. The “broad coverage” drivers openSUSE installed by default worked OK from a connectivity perspective, but did not work with the cosmetic features.
Same here, can’t confirm any bug. All well.
O.K. When I go for Wlan I get also:
Tipo: 802.11 senza fili Stato della connessione:
Connesso Indirizzo IP: 19x.16x.15x.2x
Velocità di connessione: 135 MBit/s
Nome di sistema: wlan0 Indirizzo
MAC: xx:xx:xx:xx:xx:xx
Driver: iwlwifi Punto d'accesso (SSID): downunder
Punto d'accesso (MAC): xx:xx:xx:xx:xx:xx
Banda: b/g Canale: 4 (2427 MHz)
But the traffic line stays flat. But with VPN activated the traffic and connection time of openVPN should be shown instead I get:
Tipo: non disponibile
Stato della connessione: non disponibile
Indirizzo di rete (IP): non disponibile
Velocità di connessione: non disponibile
Nome di sistema: non disponibile
Indirizzo hardware (MAC): non disponibile
Driver: non disponibile
Of course the addresses where anonimized. Version 12.2, this for 32 bit and 64 bit, KDE desktop environment, 4.10 (32bit) and 4.9.5. (64 bit), several VPN providers. Reproducible with me always. So Wlan shows but not the traffic graphics, eth as well, no traffic. The traffic graphics is just flat. And VPN shows nothing at all, no ip, connection time, nothing. Shouldn’t the openVPN show the IP of the VPN provider? And shouldn’t the traffic of the openVPN correspond to the traffic of the interface (minus some few bite)?
After some updates the file /usr/share/kde4/apps/ksysguard/SystemLoad2.sgrd is updated incorrectly.
The following is the file on this laptop (with line numbers added)
lines 12 - 15 have had to be added / modified to correctly obtain the network status monitoring history
HTH
01 <?xml version="1.0" encoding="UTF-8"?>
02 <!DOCTYPE KSysGuardWorkSheet>
03 <WorkSheet title="System Load" interval="0.5" locked="1" rows="3" columns="1">
04 <host port="-1" command="ksysguardd" shell="" name="localhost"/>
05 <display title="CPU History" version="1" row="0" class="FancyPlotter" hScale="6" unit="" showUnit="0" column="0" autoRange="0" hLines="1" manualRange="0" vScroll="0" svgBackground="widgets/plot-background" vLines="0" vDistance="30" stacked="0" labels="1">
06 <beam sensorType="float" hostName="localhost" regexpSensorName="cpu/cpu.*/TotalLoad" color="0xff0000ff,0xff008000,0xfff3c300,0xffff0000"/>
07 </display>
08 <display title="Memory and Swap History" version="1" row="1" class="FancyPlotter" hScale="6" unit="" showUnit="0" column="0" autoRange="0" hLines="1" manualRange="0" vScroll="0" svgBackground="widgets/plot-background" vLines="0" vDistance="30" stacked="0" labels="1">
09 <beam sensorName="mem/physical/application" sensorType="integer" hostName="localhost" summationName="Memory" color="0xff844798"/>
10 <beam sensorName="mem/swap/used" sensorType="integer" hostName="localhost" summationName="Swap" color="0xff00c000"/>
11 </display>
12 <display title="Network History" svgBackground="widgets/plot-background" autoRange="1" class="FancyPlotter" column="0" row="2" version="1" min="0" max="20" manualRange="1">
13 <beam sensorType="float" hostName="localhost" summationName="Receiving" regexpSensorName="network/interfaces/(?!lo|bridge|usbus|bond).*/receiver/data" color="0xB3A52D" />
14 <beam sensorType="float" hostName="localhost" summationName="Sending" regexpSensorName="network/interfaces/(?!lo|bridge|usbus|bond).*/transmitter/data" color="0x844798" />
15 </display>
16 </WorkSheet>
Trying to sort this out. Upt to now however everything seems perfectly normal. Kde Sysguard
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE KSysGuardWorkSheet>
<WorkSheet title="System Load" interval="0.5" locked="1" rows="3" columns="1" >
<host port="-1" command="ksysguardd" shell="" name="localhost" />
<display title="CPU History" svgBackground="widgets/plot-background" autoRange="0" class="FancyPlotter" column="0" row="0" version="1">
<beam sensorType="float" hostName="localhost" regexpSensorName="cpu/cpu.*/TotalLoad" color="0xffff8000,0xffe20800" />
</display>
<display title="Memory and Swap History" svgBackground="widgets/plot-background" autoRange="0" class="FancyPlotter" column="0" row="1" version="1" >
<beam summationName="Memory" sensorName="mem/physical/application" sensorType="integer" hostName="localhost" color="0xffc000c0" />
<beam summationName="Swap" sensorName="mem/swap/used" sensorType="integer" hostName="localhost" color="0xff00c000" />
</display>
<display title="Network History" svgBackground="widgets/plot-background" autoRange="1" class="FancyPlotter" column="0" row="2" version="1" min="0" max="20" manualRange="1">
<beam sensorType="float" hostName="localhost" summationName="Receiving" regexpSensorName="network/interfaces/(?!lo|bridge|usbus|bond).*/receiver/data" color="0xB3A52D" />
<beam sensorType="float" hostName="localhost" summationName="Sending" regexpSensorName="network/interfaces/(?!lo|bridge|usbus|bond).*/transmitter/data" color="0x844798" />
</display>
</WorkSheet>
But instead the ksysgard complains all the time that it
cannot open /etc/mtab
The files /usr/share/kde4/apps/ksysguard/SystemLoad2.sgrd
are identical on both machines, so that’s a red herring
On this laptop the /etc/mtab is a link to file /proc/self/mounts
which is a file of 0 B (no contents)
can only suggest you create a file /proc/self/mounts, if it does not exist,
and then create a link named /etc/mtab to it
A bit more of the story
For each user two files from /usr/share/kde4/apps/ksysguard/
are copied into /home/<username>/.kde4/share/apps/ksysguard/
on a new install each user should have two files in the home directory
ProcessTable.sgrd
and
SystemLoad2.sgrd
these files can be changed on user preferences
it is the second of the two files which have been found to be disturbed
during updagtes
if something is amiss, manually re-copying these two files should
restore the default setup
I am using secure file permissions and have altered the default permissions of the home directory in the sense that they are 700. If the two files you are talking about have to have a specific permission, this might be the reason. You do not know by any chance what file permissions they should have to be fully functional? Not said that I decide to change the permissions but I would like to understand if this could be the problem or if the update process might be the problem. Thanks in advance.
The normal user needs read and write access to these file in
the /home/<name>/ dir,
hence 700 should be ok, as its only the owner needing access
(having the execute flag set is not needed)
System Monitor is always running by default on my set-up and quite often
the System Load panel looses the Network History read/write traces and also
the history info in the Network Interface Traffic display
This seems to occur after a major NetworkManager update but not always
it maybe its disturbed after a change of trace colours and an update