Robert, can you please provide complete steps to reproduce this bug? My
understanding from discussion elsewhere that this is specific to oem-
config mode; is that correct?
If your network is incorrectly configured and you have a route to the
Internet but traffic is dropped, it is expected that an initial
connection to the apt mirror will have to hit a tcp connection timeout
(by default, ~128 seconds); so that might qualify as "several minutes".
What behavior are you seeing that is "too long", and how long do you
expect this to take?
** Changed in: ubiquity (Ubuntu)
Status: New => Incomplete
--
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:
New
Status in ubiquity package in Ubuntu:
Incomplete
Status in apt source package in Bionic:
New
Status in ubiquity source package in Bionic:
New
Bug description:
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
