Bug 817767

Summary:	Transmission ignores rate limits
Product:	[Fedora] Fedora	Reporter:	Christoph Wickert <christoph.wickert>
Component:	transmission	Assignee:	Rahul Sundaram <metherid>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	bct, charles, jeff.raber, jspaleta, kumarpraveen.nitdgp, metherid, raghusiddarth, sanjay.ankur
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-20 02:33:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Christoph Wickert 2012-05-01 07:57:49 UTC

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 15:12:53 UTC

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 16:22:10 UTC

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-20 02:33:50 UTC

Closing this since upstream is already tracking this issue and there is no fix available yet.