For-sale software won't install from software center
I purchased Bridge Construction Set (big fan of bridge games) which is my first purchase from the Ubuntu Software Center. All other application installs worked fine, I've had no issues. When trying to install the bridge construction set, however, it's an endless loop of "bridge construction set (already purchased) installing purchase..." and then "updating cache downloading 0B of 7B" in the In process tab. the updating cache item appears, closes, then reappears. It does the same thing on my desktop, and my netbook which I tried just to test and see if it was computer specific.
I ran apt-get update, here is the output of the area that gets an error:
Err https:/
SSL connection timeout at 117506
Ign https:/
Ign https:/
Fetched 522 kB in 1min 10s (7,423 B/s)
W: Failed to fetch https:/
E: Some index files failed to download. They have been ignored, or old ones used instead.
I am using Natty, 11.04
Thanks for the help, I really want to build some bridges!
Question information
- Language:
- English Edit question
- Status:
- Needs information
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Related FAQ:
None Link to a FAQ
Revision history for this message
|
#1 |
If you run:
sudo apt-get update; sudo apt-get upgrade
Is it smooth?
Revision history for this message
|
#2 |
the sudo apt-get update is pretty smooth, except for the part immediately prior to and during the errors, which seems like it's waiting to download or do something.
Sudo apt-get upgrade happens too quick for me to tell if it's smooth or not, I guess yes.
james@Zeus:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Just now I've tried to install a free program from the software center, and it downloads just fine.
Revision history for this message
|
#3 |
Ok, so I've waited through the entire endless loop of trying to download the cache, and eventually (about 45min) this message appears:
Failed to download repository information
Check your Internet connection.
Details:
W:Failed to fetch https:/
, E:Some index files failed to download. They have been ignored, or old ones used instead.
My internet connection is working fine, and I can download other programs. I'm at a loss, other than perhaps the server for purchased software is down or something. I just paid $20 for this, I'm rather disappointed. :(
Revision history for this message
|
#4 |
Thanks!
Could you please run (in a terminal):
$ sudo apt-get update -o Debug::
and attach the file /tmp/log ? This appears to be another instance of bug https:/
Revision history for this message
|
#5 |
Michael,
Thanks for the info. I've spotted bug 804900 a while ago, and it seems to be the same error. (I also clicked the "this affects me too" button.) I've pasted the log file output below.
* About to connect() to private-
* Trying 91.189.90.217... Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
* connected
* Connected to private-
Hit http://
Get:1 http://
Get:2 http://
* found 142 certificates in /etc/ssl/
Hit http://
Hit http://
Hit http://
Hit http://
Get:3 http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Get:4 http://
Hit http://
Ign http://
Hit http://
Ign http://
Hit http://
* SSL connection timeout at 115718
* Closing connection #0
Ign https:/
* About to connect() to private-
* Trying 91.189.90.217... Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Get:5 http://
Ign http://
Ign http://
* connected
* Connected to private-
* found 142 certificates in /etc/ssl/
Hit http://
Hit http://
Ign http://
Ign http://
Ign http://
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Ign http://
Ign http://
Ign http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Hit http://
Ign http://
Ign http://
* SSL connection timeout at 117726
* Closing connection #0
Ign https:/
* About to connect() to private-
* Trying 91.189.90.217... Ign http://
Ign http://
* connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117724
* Closing connection #0
Ign https:/
* About to connect() to private-
* Trying 91.189.90.217... Ign http://
Ign http://
Ign http://
* connected
* Connected to private-
* found 142 certificates in /etc/ssl/
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
* SSL connection timeout at 117723
* Closing connection #0
Ign https:/
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117718
* Closing connection #0
Ign https:/
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117725
* Closing connection #0
Ign https:/
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
* SSL connection timeout at 117720
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... Ign http://
Ign http://
Ign http://
Ign http://
* connected
* Connected to private-
* found 142 certificates in /etc/ssl/
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
Ign http://
* SSL connection timeout at 117727
* Closing connection #0
Ign https:/
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117735
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117717
* Closing connection #0
Ign https:/
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117738
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117718
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117736
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117719
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117703
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117716
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117722
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117736
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117714
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 115940
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117721
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117717
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117728
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117730
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117717
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117699
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117721
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117732
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117721
* Closing connection #0
Err https:/
SSL connection timeout at 117721
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117724
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 114726
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117719
* Closing connection #0
Err https:/
SSL connection timeout at 117719
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117717
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117697
* Closing connection #0
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117720
* Closing connection #0
Ign https:/
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117694
* Closing connection #0
Ign https:/
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 117714
* Closing connection #0
Ign https:/
* About to connect() to private-
* Trying 91.189.90.217... * connected
* Connected to private-
* found 142 certificates in /etc/ssl/
* SSL connection timeout at 116047
* Closing connection #0
Ign https:/
Fetched 15.1 kB in 2min 13s (113 B/s)
W: Failed to fetch https:/
W: Failed to fetch https:/
E: Some index files failed to download. They have been ignored, or old ones used instead.
Revision history for this message
|
#6 |
Thanks a lot for this update! So it looks like for some reason something blocks access to the private PPA server.
Could you please try to hit the follow URL with your regular browser:
https:/
and let me know if that works (you should see a empty directory).
Then please open a terminal and run:
$ curl https:/
$ w3m -dump https:/
and let me know if that works too?
Is there anything unusual you can think off about your network setup? A firewall, a proxy server
or anything like this?
Thanks,
Michael
Revision history for this message
|
#7 |
I should add that I'm really sorry for the trouble you are currently experiencing and that try all we can to find the cause of this issue.
Revision history for this message
|
#8 |
Michael, thanks for the help thus far. I switched to ubuntu because I realized the only thing I had been keeping windows for was games, and I can use dual boot for that. I hadn't used linux since 2003 (suse) and thought it'd be a good change. I really like the open source concept, and I like having more control over my OS. I expected to experience hiccups, and maybe this issue will help people in the future with the same problem, or maybe even improve the next version of Ubuntu. So it's worth the wait :)
I don't have any particularly special setup. I have a wired connection for my desktop, to a router, and from that to my cable modem. The only thing that I can think of that may cause an issue is my latency, which is very large. (about 600ms to anchorage, and 600ms back) I'm a meteorologist, and I work for the NWS in a remote Alaskan town, so all telecommunications are routed via satellite to anchorage. perhaps the latency causes the delay to be to long when authenticating? Now on to your suggestions
I connected to https:/
I didn't have curl or w3m installed, so I installed them.
james@Zeus:~$ curl https:/
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html>
<head>
<title>Index of /mvo</title>
</head>
<body>
<h1>Index of /mvo</h1>
<table><tr><th><img src="/icons/
<tr><td valign="top"><img src="/icons/
<tr><th colspan=
</table>
<address>
</body></html>
james@Zeus:~$ w3m -dump https:/
Index of /mvo
[ICO] Name Last modified Size
━━━━━━━
[DIR] Parent Directory -
━━━━━━━
Apache/2.2.14 (Ubuntu) Server at private-
Revision history for this message
|
#9 |
Thanks for the additional info! The latency may well be a important hint here. Its puzzling however that both w3m and curl seem to connect just fine, apt uses the same library for the https as curl (but probably with different options, now we just need to find out what they are :)
Could you please see if:
$ sudo apt-get update -o Acquire:
(or Timeout=999999 or some other ridiculous large value) make a difference
Thanks,
Michael
Revision history for this message
|
#10 |
I first tried
sudo apt-get update -o Acquire:
That still timed out, so I tried "9999999" and got pretty much the same error except with a larger timeout number:
Err https:/
SSL connection timeout at 9999996720
Err https:/
SSL connection timeout at 9999996721
maybe it's an issue where the server asks for authentication, but the apt-get doesn't respond soon enough (because of extra latency) so authentication fails, and the process repeats until it times out. That's just a guess though.
I'm going to work now, I'll check back when I get home.
Revision history for this message
|
#11 |
Thanks again, I was just talking to our server team and they asked me to do a apt-get update and "w3m https:/
Many thanks!
Michael
Revision history for this message
|
#12 |
I've ran the commands and got my external IP address. the w3m went through fine and showed the empty directory.
My external IP address is:
24.237.125.118
Revision history for this message
|
#13 |
I ran into more or less the same problem this evening (except that I was trying to install Braid). After completing my purchase in the Ubuntu Software Centre, the process timed out without enabling an Install link. I received a purchase confirmation email a few moments later, however, which included a link to a troubleshooting page with info about the private ppa I needed to add to my software sources. So I dutifully added the ppa to /etc/apt/
I have no idea why, but for some reason a simple reboot seems to have cured the problem for me on both machines, and each of them now has Braid installed. So if by some chance you haven't rebooted recently, give that a try. Also, make sure your private ppa is authenticated (the troubleshooting link in your purchase confirmation email should have some information about the OpenPGP key your repository is signed with).
Cheers,
BBB
Revision history for this message
|
#14 |
Thanks bob for the info, I'll try checking that out again after work to see if I missed anything before.
Revision history for this message
|
#15 |
Sorry for the late reply, wife and kids attacked yesterday afternoon. I went through the sources and made sure they were listed, and added them again just to be sure. despite this, I had no luck. The only thing I can think of is the authentication. I've seen that openPGP key number, but don't see it listed in the authentication tab. The only option to add a key seems to be from a keyfile, not a manual number code.
Also, I turn off my machine every day, so I know it's not a restart issue.
Revision history for this message
|
#16 |
Hi James,
At the bottom of the purchase confirmation email you received, there should be an https troubleshooting link. Open the link in your browser. Below the deb line for the software you purchased, it should say something like "This repository is signed with OpenPGP key 1024R/75254D99". The part after the slash is what you're interested in. Open a terminal, enter the part following the slash it in a command like "sudo apt-key adv --keyserver keyserver.
Revision history for this message
|
#17 |
I attempted the command using the key in the troubleshooting page. Afterwards there was no change in the bug.
james@Zeus:~$ sudo apt-key adv --keyserver keyserver.
[sudo] password for james:
Executing: gpg --ignore-
gpg: requesting key 75****** from hkp server keyserver.
gpg: key 75******: "Launchpad test" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
Revision history for this message
|
#18 |
got the same problem with 'familyfarm', paid $15 for it, but it won't install, messages are in Dutch, but I think they're the same:
W: Ophalen van https:/
W: Ophalen van https:/
W: Ophalen van https:/
E: Some index files failed to download. They have been ignored, or old ones used instead.
sudo apt-key adv --keyserver keyserver.
Executing: gpg --ignore-
gpg: opvragen sleutel 75254D99 van hkp sleutelserver keyserver.
gpg: sleutel 75254D99: “Launchpad test” niet veranderd
gpg: Totaal aantal verwerkt: 1
gpg: Onveranderd: 1
Revision history for this message
|
#19 |
If you click those links, you are asked for a username and password.Maybe that is a factor
Revision history for this message
|
#20 |
I only receive some meaningless text, now the download won't even start from the softwarecenter
Can you help with this problem?
Provide an answer of your own, or ask James Ellis for more information if necessary.