Don't attempt to connect to time-server when no wireless connection
Bug #626003 reported by
Greg Grossmeier
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubiquity (Ubuntu) |
Expired
|
High
|
Unassigned | ||
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.
Revision history for this message
| Craig Maloney (craig-decafbad) wrote | #1 |
| Changed in ubiquity (Ubuntu): | |
| status: | New → Confirmed |
| Changed in ubiquity (Ubuntu): | |
| assignee: | nobody → Evan Dandrea (ev) |
| importance: | Undecided → High |
| status: | Confirmed → Triaged |
| tags: | added: iso-testing |
| Changed in ubiquity (Ubuntu): | |
| assignee: | Evan Dandrea (ev) → nobody |
Revision history for this message
| Marcus Tomlinson (marcustomlinson) wrote | #3 |
| Changed in ubiquity (Ubuntu): | |
| status: | Triaged → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in ubiquity (Ubuntu): | |
| status: | Incomplete → Expired |
To post a comment you must log in.
Saw this behavior on two machines that were not connected to the network.