Bug 817767 - Transmission ignores rate limits
Transmission ignores rate limits
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: transmission (Show other bugs)
17
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Rahul Sundaram
Fedora Extras Quality Assurance
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-01 03:57 EDT by Christoph Wickert
Modified: 2013-01-19 21:33 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-01-19 21:33:50 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Christoph Wickert 2012-05-01 03:57:49 EDT
Description of problem:
In F17, transmission ignores download and upload limits.

Version-Release number of selected component (if applicable):
transmission-2.50-2.fc17.x86_64
transmission-cli-2.50-2.fc17.x86_64
transmission-common-2.50-2.fc17.x86_64
transmission-gtk-2.50-2.fc17.x86_64

How reproducible:
always

Steps to Reproduce:
1. Start some file transfers.
2. Limit the download rate
  
Actual results:
Rate does not go down. This us fully reproducible.

Expected results:
Rate should go down to the limit.

Additional info:
I never hat this problem in earlier versions, that's why I consider it a regression.
Comment 1 Jeff Raber 2012-06-19 11:12:53 EDT
Are you having this problem with torrent that includes a 'webseed'?  If so, this is a known issue in Transmission.

See: https://trac.transmissionbt.com/ticket/1079
Comment 2 Christoph Wickert 2012-06-19 12:22:10 EDT
I can confirm I only have this problem with some torrents, but how do I know if it includes a webseed? AFAIR it was one of the F17 ISOs.
Comment 3 Rahul Sundaram 2013-01-19 21:33:50 EST
Closing this since upstream is already tracking this issue and there is no fix available yet.

Note You need to log in before you can comment on or make changes to this bug.