Bug 450376

Summary: Knetstats shows very high bandwidth usage sometimes
Product: [Fedora] Fedora Reporter: Kulbir Saini <kulbirsaini25>
Component: knetstatsAssignee: Chitlesh GOORAH <chitlesh>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 7   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-07 14:57:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Image showing the awkward behavior none

Description Kulbir Saini 2008-06-07 08:16:00 UTC 
Description of problem:
Sometimes when I reload my wifi module or restart my network, knetstats unusual
transfer speeds in the graph window. Checkout the screenshot attached for more
details.

Version-Release number of selected component (if applicable):
knetstats-1.5-1.2.fc7.rf

How reproducible:
Sometimes when network is restarted.

Steps to Reproduce:
1. Restart the network
2. Open knetstats and you'll get it if you are lucky :)
3.
  
Actual results:
Very high transfer speed (millions of MB/sec)

Expected results:
Actual transfer speed on interface


Additional info:
Comment 1 Kulbir Saini 2008-06-07 08:16:00 UTC 
Created attachment 308590 [details]
Image showing the awkward behavior
Comment 2 Chitlesh GOORAH 2008-06-07 14:57:06 UTC 
I'm sorry to close this bug, because you are NOT using a knetstats package
coming _from_ Fedora.

Your knetstats version is : knetstats-1.5-1.2.fc7.rf

".rf" is NOT from fedora.

Fedora's latest knetstats version is : knetstats-1.6.1-3.fc7

http://koji.fedoraproject.org/koji/packageinfo?packageID=2231

Please use Fedora only packages in the future to avoid such silly bugs.
Comment 3 Kulbir Saini 2008-06-07 17:07:31 UTC 
yeah .. the bug was surely a silly one :P