ubuntu-download-manager is reporting the wrong total size during downloads, via its progress signal
Bug #1450144 reported by
Pat McGowan
This bug affects 16 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
High
|
Bill Filler | ||
Capomastro |
Incomplete
|
Medium
|
Unassigned | ||
Ubuntu system image |
Incomplete
|
Medium
|
Unassigned | ||
ubuntu-download-manager |
Fix Released
|
High
|
Michael Sheldon |
Bug Description
When downloading updates the UI shows progress in a size much larger than the actual amount of bytes downloaded. Assuming that the headers are providing incorrect information.
Possible duplicates: bug 1420853, bug 1429022, bug 1442857, bug 1456110
Related branches
lp:~michael-sheldon/ubuntu-download-manager/fix-content-length-detection
- PS Jenkins bot: Approve (continuous-integration)
- Ubuntu Phablet Team: Pending requested
-
Diff: 11 lines (+1/-0)1 file modifiedsrc/downloads/priv/ubuntu/downloads/file_download.cpp (+1/-0)
Changed in capomastro: | |
status: | New → Confirmed |
tags: | added: stakeholder |
Changed in capomastro: | |
importance: | Undecided → Medium |
Changed in capomastro: | |
milestone: | none → future |
summary: |
- server is reporting the wrong size during downloads + ubuntu-download-manager is reporting the wrong total size during + downloads |
summary: |
ubuntu-download-manager is reporting the wrong total size during - downloads + downloads, via its progress signal |
description: | updated |
description: | updated |
Changed in canonical-devices-system-image: | |
milestone: | none → ww40-2015 |
Changed in ubuntu-download-manager: | |
assignee: | nobody → Manuel de la Peña (mandel) |
Changed in canonical-devices-system-image: | |
assignee: | John McAleely (john.mcaleely) → Bill Filler (bfiller) |
milestone: | ww40-2015 → backlog |
Changed in ubuntu-download-manager: | |
assignee: | Manuel de la Peña (mandel) → Michael Sheldon (michael-sheldon) |
Changed in canonical-devices-system-image: | |
status: | Confirmed → In Progress |
Changed in ubuntu-download-manager: | |
status: | Confirmed → In Progress |
Changed in canonical-devices-system-image: | |
milestone: | backlog → ww02-2016 |
Changed in canonical-devices-system-image: | |
status: | In Progress → Confirmed |
status: | Confirmed → Fix Committed |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
Changed in ubuntu-download-manager: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Hi Pat,
I tried using curl to download a custom tarball.
First I got only the headers to check the content-length:
roadmr@ blackdog: /tmp$ curl --head https:/ /sis.capomastro .canonical. com/pool/ custom- 3ed576bc5513430 feab7a10b370d1d 5fcade19fb00bf1 d7f39b0d6451c7f 26a5.tar. xz 514c0545e921b"
HTTP/1.1 200 OK
Date: Tue, 12 May 2015 13:46:33 GMT
Server: Apache/2.4.7 (Ubuntu)
Last-Modified: Tue, 28 Apr 2015 03:19:25 GMT
ETag: "39373f0-
Accept-Ranges: bytes
Content-Length: 59995120
Content-Type: application/x-tar
Next I downloaded the tarball, curl's progress bar and estimates looked OK to me:
roadmr@ blackdog: /tmp$ curl --output custom.tar.xz https:/ /sis.capomastro .canonical. com/pool/ custom- 3ed576bc5513430 feab7a10b370d1d 5fcade19fb00bf1 d7f39b0d6451c7f 26a5.tar. xz
Dload Upload Total Spent Left Speed
% Total % Received % Xferd Average Speed Time Time Time Current
100 57.2M 100 57.2M 0 0 751k 0 0:01:17 0:01:17 --:--:-- 1039k
Finally I checked the file size matched what the header told me initially:
roadmr@ blackdog: /tmp$ ls -la custom.tar.xz
-rw-rw-r-- 1 roadmr roadmr 59995120 May 12 09:48 custom.tar.xz
I also checked the index.json for the channel (ubuntu- touch/tangxi- vivid-proposed) and device (arale), I found this:
{
" checksum" : "3ed576bc551343 0feab7a10b370d1 d5fcade19fb00bf 1d7f39b0d6451c7 f26a5",
" order": 1,
" path": "/pool/ custom- 3ed576bc5513430 feab7a10b370d1d 5fcade19fb00bf1 d7f39b0d6451c7f 26a5.tar. xz",
" signature" : "/pool/ custom- 3ed576bc5513430 feab7a10b370d1d 5fcade19fb00bf1 d7f39b0d6451c7f 26a5.tar. xz.asc" ,
" size": 59995120
},
so it looks like sizes match everywhere, at least for the custom tarball.
Did you see this with any other components? perhaps the device or ubuntu tarballs?
Did you see this with a delta? if so, could you tell me which version you were at, and which version it was upgrading you to? That way I can hunt down the deltas in the index and check them with the same process.