NetworkManager is starting up "after" ubiquity in only-ubiquity mode
Bug #277302 reported by
Mario Limonciello
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
ubiquity (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
Currently the NetworkManager init script happens during runlevels with priority 30. Ubiquity's happens at 29. Because of this, only-ubiquity and automatic-ubiquity will fail to have network connectivity.
The side effect of this is that the update at the end of ubiquity doesn't actually get performed.
The proposed runlevel priority would then be 28. This ensures that ubiquity will come after Network Manager.
Changed in ubiquity: | |
status: | New → Invalid |
Changed in network-manager: | |
importance: | Undecided → Medium |
status: | New → Triaged |
To post a comment you must log in.
Is this in 8.10?