Don't attempt to connect to time-server when no wireless connection

Bug #626003 reported by Greg Grossmeier on 2010-08-28
This bug affects 3 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)

Bug Description

Binary package hint: ubiquity

During install it has already been determined that there is no wired/wireless connection. Later it attempts to set the time based on a time server. This should be skipped so the user isn't wondering why it is attempting to make a connection when the system "knows" it isn't possible.

Craig Maloney (craig-decafbad) wrote :

Saw this behavior on two machines that were not connected to the network.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Evan (ev) wrote :

ubiquity should set tzsetup/geoip_server to null and clock-setup/ntp to false when it cannot detect an Internet connection. It should reset these values when a connection becomes available.

Changed in ubiquity (Ubuntu):
assignee: nobody → Evan Dandrea (ev)
importance: Undecided → High
status: Confirmed → Triaged
tags: added: iso-testing
Evan (ev) on 2012-03-15
Changed in ubiquity (Ubuntu):
assignee: Evan Dandrea (ev) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers