This bug was fixed in the package apt - 1.6.2
---------------
apt (1.6.2) unstable; urgency=medium
* Fix build with new gtest (Closes: #897149)
* Handle a missed case of timed out ip addresses (LP: #1766542)
* Lower default network timeouts from 120s to 30s
* apt-key: Pass all instead of gpg-agent to gpgconf --kill (LP: #1773992)
* Fix lock counting in debSystem (LP: #1778547)
* CI fixes:
- tests: Do not expect requested-by if sudo was invoked by root
- Run tests on GitLab CI
- CI: Export DEBIAN_FRONTEND=noninteractive in all CI environments
-- Julian Andres Klode <juli...@ubuntu.com> Mon, 25 Jun 2018 17:15:10
+0200
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1766542
Title:
Installation blocks when the machine is behind a proxy server
Status in OEM Priority Project:
Confirmed
Status in apt package in Ubuntu:
Fix Released
Status in ubiquity package in Ubuntu:
Incomplete
Status in apt source package in Bionic:
Fix Released
Status in ubiquity source package in Bionic:
New
Bug description:
[Impact]
APT takes a long time to notice when certain connections time out
[Test case]
* Change the default route to not route stuff successfully (wrong gateway,
for example)
* Make your sources.list look like this:
deb http://archive.ubuntu.com/ubuntu bionic main restricted
deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted
* Run apt update
You should see that it fails with a long verbose error message for the
first entry, with all possible IP addresses listed in it; while for
the second one it fails with just "Unable to connect to
archive.ubuntu.com:http:" as it recognizes it has been blacklisted.
[Regression potential]
APT will not attempt to retry the host given that it could not connect to it
for previous entries. If your network recovered in the meantime, it might
update less than previously.
[Original bug report]
When the machine is behind a proxy server, the installation will block for a
while (several minutes) to retrieve the package lists. The timeouts are too
long and makes user feels the machine may have some problems.
The symptom is similar with bug #14599, but it seems the apt-setup
module was rewritten.
Another method to trigger this issue is to make the machine cannot
access to the Internet, for instance: a wrong gateway.
Image: 16.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1766542/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
