NetworkManager is starting up "after" ubiquity in only-ubiquity mode

Bug #277302 reported by Mario Limonciello on 2008-10-02
266
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Medium
Unassigned
ubiquity (Ubuntu)
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
Luke Faraone (lfaraone) wrote :

Is this in 8.10?

Mario Limonciello (superm1) wrote :

Yes

Luke Faraone (lfaraone) on 2008-10-02
Changed in network-manager:
importance: Undecided → Medium
status: New → Triaged
Mario Limonciello (superm1) wrote :

I've linked a bzr branch to this bug. I've tested the attached changes in a custom built live CD with the network manager updated package included. I've verified that (wired) network is now available in only-ubiquity.

Changed in network-manager:
milestone: none → ubuntu-8.10
Colin Watson (cjwatson) wrote :

I agree (Mario and I talked about this on IRC beforehand).

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package network-manager - 0.7~~svn20081015t024626-0ubuntu1

---------------
network-manager (0.7~~svn20081015t024626-0ubuntu1) intrepid; urgency=low

  new upstream snapshot Wed 2008-10-15 02:46:26 +0000 (bzrrev 3637); topic:
  - more vpn and routing fixes

  [ Alexander Sack <email address hidden> ]
  * drop upstreamed IFUPDOWN patches
    - delete debian/patches/003-IFUPDOWN-remove-unused-callbacks.loom.patch
    - delete debian/patches/004-IFUPDOWN-devtracking.loom.patch
    - delete debian/patches/005-IFUPDOWN-unmanaged-mode.loom.patch
    - delete debian/patches/006-IFUPDOWN-parse-system-settings.loom.patch
    - delete debian/patches/007-IFUPDOWN-managed-mode.loom.patch
  * adjust patches that didnt apply cleanly anymore
    - update debian/patches/008-BACKEND-debian-fallback-to-generic-loopback.loom.patch
  * fix eventual restart races by --retry'ing at least 5 seconds for NM to stop
    in init script

  [ Mario Limonciello <email address hidden> ]
  * debian/network-manager.postinst:
    - Set startup priority to be lower than Ubiquity to allow only-ubiquity
      installs to have network access. (LP: #277302)

 -- Alexander Sack <email address hidden> Thu, 16 Oct 2008 00:08:41 +0200

Changed in network-manager:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public Security information  Edit
Everyone can see this security related information.

Duplicates of this bug

Other bug subscribers