Still over 7 months after the OP, I too am experiencing the same problem. Luckily the suggestion in post #36 seems to have SOLVED it, but this is ONLY A WORKAROUND. I also have AT&T (ugh!) and it seems AT&T's DNS servers are just too slow. I was able to manually set the Google DNS servers on my AT&T 2wire router, which is nice because this will solve the same problem for all machines on my network now. ... Hopefully this change will have the additional side effect of increasing my overall network latency (which previously sucked!).
But still... APT should definitely tweak it's settings to allow longer timeouts, or to retry a couple times after failure. No other network- connected software had problems with AT&T's crappy latency, so clearly APT is failing to accommodate such poor connections. Does anyone out there know if these parameters are configurable? If so, how, and where? ... and if such a fix works, why aren't those defaults correctly configured in Maverick? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/574886 Title: Apt has strange network errors when updating indexes. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
