Comment 6 for bug 172879

I had the same problem on a networking environment, where the configuration is assigned by DHCP, but even the DNS service is unavailable. This network setup requires using SOCKS proxy on IP-only adressed server. The installation stalled at 82% and seemed to not move anymore. The error message, which appeared after long time of waiting, claimed that apt didn't find some repositories on disk (in polish), though the problem was indeed unaccesible network repository, so that was clearly misreported. When I clicked OK on the message window nothing else happened for so long, that I stopped waiting.

The workaround was to manually disable networking in Network Manager.

Proposed actions:

1. The error message has to be exact and correct

2. Skipping just this step would be essential, probably with information what's going on ("looking for a server", "waiting for a server" etc), with reasonable connection timeout (maybe 30 s visible counter?) and offering user a choice, not just the plain error message ("Server timed out, try again? - Yes/Skip this step/Cancel installation")

3. The way to configure SOCKS for installer/apt would be preferable