purchased software download fails with and breaks apt proxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt-cacher-ng (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Maverick |
Invalid
|
Undecided
|
Unassigned | ||
Natty |
Invalid
|
Undecided
|
Unassigned | ||
software-center (Ubuntu) |
Fix Committed
|
Undecided
|
Unassigned | ||
Maverick |
Invalid
|
High
|
Unassigned | ||
Natty |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: software-center
I used Software Center -> Get Software -> For Purchase and bought "Ricks Wallpapers" for $1.00 USD. The purchase process went fine, but the install failed, and has now left my apt cache in a bad state.
After the purchase process, Software Center spun its wheels for a very long time (several minutes) until finally a popup error window delivered this error:
W: Failed to fetch https:/
cks-wallpaper/
aborted
E: Some index files failed to download, they have been ignored, or old ones used
instead.
'sudo apt-get update' also fails with the same error message.
The problem apparently occurs because of my apt-cache-ng proxy setup (which works fine otherwise). I have a one line file /etc/apt/
Acquire::http { Proxy "http://
If I disable my apt proxy by commenting out the Acquire line, then I am able to install "Ricks Wallpapers" from Software Center. And 'apt-get update' then yields only "Ign https:/
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: software-center 3.0
ProcVersionSign
Uname: Linux 2.6.35-23-generic x86_64
Architecture: amd64
Date: Fri Sep 24 16:09:50 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
PackageArchitec
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: software-center
Related branches
Changed in software-center (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → ubuntu-10.10 |
Changed in software-center (Ubuntu): | |
milestone: | ubuntu-10.10 → maverick-updates |
Changed in software-center (Ubuntu Natty): | |
milestone: | maverick-updates → none |
Changed in software-center (Ubuntu Maverick): | |
milestone: | none → maverick-updates |
Changed in software-center (Ubuntu Natty): | |
status: | Confirmed → New |
Changed in software-center (Ubuntu Maverick): | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in software-center (Ubuntu Natty): | |
importance: | High → Undecided |
Changed in software-center (Ubuntu Maverick): | |
status: | Confirmed → Fix Committed |
Changed in software-center (Ubuntu Natty): | |
status: | New → Fix Committed |
Changed in apt-cacher-ng (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in apt-cacher-ng (Ubuntu Maverick): | |
status: | Confirmed → Invalid |
Changed in lucid-backports: | |
status: | New → Invalid |
no longer affects: | lucid-backports |
tags: | added: u1-support |
tags: |
added: u1-by-support u1-support-escalated removed: u1-support |
Changed in software-center (Ubuntu Natty): | |
status: | Fix Committed → Invalid |
tags: | removed: maverick |
Changed in apt-cacher-ng (Ubuntu): | |
status: | Triaged → Fix Released |
Part of the problem seems to be that we should use port 80 of keyserver. ubuntu. com, I commtied a fix for this. The rest needs a bit of debugging love, I will do that tomorrow.