multiple download works strangely

Bug #295040 reported by Daniel Milde on 2008-11-07
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fix Released
transmission (Ubuntu)

Bug Description

Binary package hint: transmission

Transmission works very strangely when downloading multiple files.

T shows that is downloading 250kB/s (true), but after 8 hours downloaded just about 200MB!

Tried many times.

Charles Kerr (charlesk) wrote :

This is probably the highest priority bug fixed between 1.34 and 1.40, at least to my mind. It doesn't hit very many people, but if you're one of the lucky few, it's very annoying.

Changed in transmission:
status: Unknown → Fix Released
Daniel Milde (daniel-milde) wrote :

Great, thanks! :)

Hew (hew) wrote :

Fix included upstream with 1.40

Changed in transmission:
importance: Undecided → High
status: New → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package transmission - 1.40-0ubuntu1

transmission (1.40-0ubuntu1) jaunty; urgency=low

  * New upstream release (LP: #302672)
    - Tracker communication uses fewer resources
    - More accurate bandwidth limits
    - Reduce disk fragmentation by preallocating files (LP: #287726)
    - Stability, security and performance improvements to the RPC /
      Web UI server (closes LP: #290423)
    - Support compression when serving Web UI and RPC responses
    - Simplify the RPC whitelist
    - Fix bug that prevented handshakes with encrypted BitComet peers
    - Fix 1.3x bug that could re-download some data unnecessarily
      (LP: #295040)
    - Option to automatically update the blocklist weekly
    - Added off-hour bandwidth scheduling
    - Simplify file/priority selection in the details dialog
    - Fix a couple of crashes
    - New / updated translations
    - Don't inhibit hibernation by default (LP: #292929)
    - Use "close" animation when sending to notification area (LP: #130811)
    - Fix resize problems (LP: #269872)
    - Support "--version" option when launching from command line
      (LP: #292011)
    - Correctly parse announce URLs that have leading or trailing
      spaces (LP: #262411)
    - Display an error when "Open Torrent" fails (LP: #281463)
  * Dropped 10_fix_crasher_from_upstream.dpatch: Fix is in this
    upstream release.
  * debian/control: Don't just build-depend on libcurl-dev, which is
    a virtual package.

 -- Chris Coulson <email address hidden> Fri, 28 Nov 2008 15:33:48 +0000

Changed in transmission:
status: Fix Committed → Fix Released
Chris Coulson (chrisccoulson) wrote :

charles - Do you think it is possible to isolate the patch that fixed this bug in 1.40? It would be great to be able to backport the patch to the Intrepid 1.34 version of Transmission, so I can nominate it for a SRU.

Charles Kerr (charlesk) wrote :

I'm not sure that it's a good candidate for backporting. I'd love to see this fixed in Hardy but it's a pretty involved patch.

Sergiy Zuban (s-zuban) wrote :

Since 1.34 has the bug that makes Transmission completely unusable and forces users to switch to other programs, personally I think it doesn't matter for end user how you are going to fix the bug - backport it or make 1.40 available for all ubuntu releases where the bug occurs (assume Hardy and Intrepid). In any case we shouldn't wait until Jaunty released.

Charles Kerr (charlesk) wrote :

I'll look into it, but the reason I haven't done so already is because the backport will most likely be too much for Ubuntu's "changes should be as small as possible" rule of thumb.

Chris Coulson (chrisccoulson) wrote :

Thanks charles. I've subscribed ubuntu-sru to get their thoughts on what would be acceptable for SRU.

Martin Pitt (pitti) wrote :

Backporting the fix is of course acceptable.

Charles Kerr (charlesk) wrote :

Okay, reporting back on my findings... the backport is possible, but largish. If something
of this size is going to be accepted into Hardy, I suggest going a little further and doing
a 1.35 release specifically for Hardy, including this fix and a handful of other small but
worthy fixes. Looking over the logs, I've come up with these candidates for such a
release: That pastebin lists the bugs and URLS to
their Transmission bug tickets, which in turn have links to their diffs.

If this sounds like a good idea to the Hardy maintainers, let me know and I'll start work on it.

John Dong (jdong) wrote :

I am not ~ubuntu-sru so I can't speak on their behalf, but I think a 1.35 bugfix release for -updates would be nice; the issues in your pastebin sound like good candidates for a point release. However, make sure you coordinate with Martin / -sru to make sure you're on the same page whether you're submitting patches for each of those problems, or rolling a new version of a release. If doing the latter, make sure that ~ubuntu-sru is going to accept it before putting so much work into it.

On a tangential note I'm interested in backporting a recent version of Transmission to Intrepid if it contains worthwhile new functionality, too. This is not related at all to fixing the above bug(s) in -updates, of course.

Charles Kerr (charlesk) wrote :

Since Martin's CC'ed to this ticket, I'll wait for him to comment.

Martin Pitt (pitti) wrote :


doing a new upstream microrelease with important cherrypicks sounds excellent in general, and might also benefit other people/distros that way. In general I'm not so much concerned whether something is called 1.34+patches or 1.35, but rather whether the changes have a considerable potential to cause regressions. In general, 10 known bugs are better than introducing one new one. OTOH, with hardy being an LTS, backporting safe patches is a real benefit for users, and thus will be widely appreciated.

So we should make sure to have a good QA cycle on that, but otherwise I'm fine with this.

Thank you!

Chris Coulson (chrisccoulson) wrote :

I'm slightly confused here. Does this bug only affect 1.3x releases of transmission? If that is the case, then the SRU needs to be targetted at Intrepid (which has 1.34), instead of Hardy. Hardy is still on 1.06, and I'm not sure if 1.06 is affected by this bug.

Martin Pitt (pitti) wrote :

I don't know, Charles mentioned both hardy and intrepid.

Charles Kerr (charlesk) wrote :

I misspoke. This bug only affects [1.30...1.34], so Chris is correct about the SRU target.

Martin Pitt (pitti) on 2008-12-05
Changed in transmission:
status: New → Invalid
status: New → Triaged
Chris Coulson (chrisccoulson) wrote :

Thanks for clarifying

Changed in transmission:
importance: Undecided → High
Charles Kerr (charlesk) wrote :

Okay, I've done the backports. Most of the items in the list are one-liners
that I consider safe, but the primary reason for this work -- backporting the
overdownloading bug -- is (as predicted) a monster 1400 line diff. Who knows
how much QA is needed for that, especially since most of our active testers
have already moved onto 1.41 beta 2. I am very uncomfortable with this and
think that ~ubuntu-sru should be uncomfortable with it too.

As I said above, the overdownloading bug does not actually hit many users.
Sergiy Zuban overstates the case when he says it's "completely unusable".


Here are the safe, small low-hanging fruit 1.3x backports that I *do* endorse.
Should I make a separate ticket for this?

Chris Coulson (chrisccoulson) wrote :

Thanks charles, 1400 lines is pretty big. I have to admit, I didn't agree with the comment about the current version being completely unusable either - I wasn't even aware of the bug until I came across this report, and I've been using transmission quite happily in Intrepid.

Based on your assessment of the impact of the bug, I'll downgrade the importance for the Intrepid task

Changed in transmission:
importance: High → Medium
Charles Kerr (charlesk) wrote :

I've created a new ticket <> for those other changesets.

Sergiy Zuban (s-zuban) wrote :

In my case 80-90% downloaded data was lost. For those who have bandwidth less then 1Mbit/s difference is very noticeable - download a movie for just several hours or several days. For me it's the same as "unusable".

As temporary solution I've installed 1.40 from unofficial repo

Martin Pitt (pitti) wrote :

Thanks, charles, for these investigations. I agree, if you have to backport half of 1.40 to fix this, then it's more appropriate to request a backport of 1.40 to intrepid and thus allow people to use that.

Thanks for opening the other bug, I'll mangle it accordingly.

Changed in transmission:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.