Bug 222767

Summary: Network history graphs show meningful network activity even with wireless turned off
Product: [Applications] ksysguard Reporter: anton <benderamp>
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: johnflux
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: gnome network monitor vs kde network monitor

Description anton 2010-01-14 22:01:20 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

KDE 4.3.90 (KDE 4.4 RC1) from opensuse factory.

After updating from beta 1 I have noticed that network monitor plasmoid (I have it in the panel - show wireless, no ethernet connections) always shows active outgoing and incoming traffic even though I have no evident network activities - all torrents are stopped, no loading pages in konqueror etc. System monitor Network History shows same activity.

"sudo lsof -i | grep ESTABLISHED" and "sudo netstat -A inet --program" show no active connections.

I have killed all konqueror instances, closed ktorrent, amarok and even killed plasma-desktop - the result is the same.

I have started to think that I have a kind of rootkit in my system which hides its process from lsof and netstat utils, but after switching off wireless (by hardware button) network monitor still showed network activity (the result changed from waves to straight line, but still with non-zero value).

Another good sign for me is that gnome network monitor also does not show such network activity.

Currently KDE network monitor shows me 1Gb/s incoming traffic and 0.36Gb/s outgoing, and gnome network monitor shows 0 for outgoing and 58bytes/s changing with 0 each second for incoming (see attached screenshot).

I also did not have this on beta1.
Comment 1 anton 2010-01-14 23:00:53 UTC
Created attachment 39906 [details]
gnome network monitor vs kde network monitor
Comment 2 John Tapsell 2010-01-15 02:00:10 UTC
I think this is now fixed in RC2.  Please check in RC2 and reopen if it's still there.