@charles : It is sad to see this bug is being hand-waived without actually
giving us steps to debug the issue. and saying that the user needs to prove it
is transmissions fault!
why dont you try to give us some steps to debug this issue? and then tell us
its not transmission's fault!
there are screenshots of users facing the problem that is the info *we* can
provide.
If we knew about torrent protocols and if we knew how to debug, wouldnt we let
you know already?
The problem here is not the over-head , but why isnt transmission trying to
control the overhead even when we explicitly set the global limits?? [comment
#15]
Then what is the purpose of having a global limit if it cannot control global
transfer?
How are other clients able to control this global transfer[including over-head]
too?
Vuze does this very well, if we set a global limit then it *is* honored.
If transmission devs dont want to fix the issue, it's up to you folk.
But mentioning it as an invalid bug is wrong. This bug is *not* invalid.
We are facing the bug and we have provided the info we can. The bug is valid.
Not fixing it is upto you.. :-)
No debug info was requested , so not incomplete.
It's a wont fix rather. Its just lack of interest in debugging from the
transmission devs.
Setting as wontfix instead since the intent[comment #27] seems to just close
this bug.
** Changed in: transmission (Ubuntu)
Status: Invalid => Won't Fix
--
Transmission bit-torrent doesn't honor speed limitation preferences
https://bugs.launchpad.net/bugs/460733
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
