Bug 259836 - Speed Limit No Working
Summary: Speed Limit No Working
Status: RESOLVED DUPLICATE of bug 210694
Alias: None
Product: kget
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: KGet authors
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-14 13:51 UTC by Michalng
Modified: 2011-02-13 12:26 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Image of kget downloading speed and download speed limit setting (106.87 KB, image/png)
2010-12-14 13:51 UTC, Michalng 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Michalng 2010-12-14 13:51:31 UTC 
Created attachment 54547 [details]
Image of kget downloading speed and download speed limit setting

Version:           unspecified (using KDE 4.4.5) 
OS:                Linux

KGet Version 2.4.5  Using KDE Development Platform 4.4.5 (KDE 4.4.5)


Kget -> Settings -> Configure -> Network -> Speed Limit
The above setting does not have any effect at all.

Eg. I've set the Global Download Limit at 500K but kget still downloads at more than 500K, even after a reboot.


Reproducible: Always

Steps to Reproduce:

Kget -> Settings -> Configure -> Network -> Speed Limit

Set your limit.

Download a file e.g. googleearth

Actual Results:  
Download speed exceed the set limit

Set download speed limit at 500K but download can exceed 500K using my 10M connection.


Expected Results:  
Download speed should NOT exceed set limit.


Kget version as below :
KGet
Version 2.4.5
Using KDE Development Platform 4.4.5 (KDE 4.4.5)

Debian version as below :
Debian Squeeze
Linux 2.6.32-5-amd64 x86_64
Comment 1 Michalng 2010-12-21 13:20:58 UTC 
Just checked and confirmed that wget is working okay with speed limit e.g.

wget --limit-rate=300k http://somefile

So, Kget is the one "having" the problem.
Comment 2 Matthias Fuchs 2011-02-13 12:26:46 UTC 

*** This bug has been marked as a duplicate of bug 210694 ***