[Bug 924836] Re: network-manager does not tell plymouth it has started

[Mathieu Trudel-Lapierre]

NetworkManager indeed doesn't deal with this kind of signal, nor does it
need to, AFAIK.

Reassigning to ifupdown, that's my best guess for what goes wrong (need
to emit static-network-up AFAICT, as required by the failsafe upstart
job, which is what writes this plymouth message).

** Also affects: ifupdown (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: ifupdown (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: ifupdown (Ubuntu Precise)
       Status: New => Confirmed

** Changed in: network-manager (Ubuntu Precise)
       Status: Confirmed => Incomplete

** Changed in: ifupdown (Ubuntu Precise)
     Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/924836

Title:
  network-manager does not tell plymouth it has started

Status in “ifupdown” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Ubuntu:
  Incomplete
Status in “ifupdown” source package in Precise:
  Confirmed
Status in “network-manager” source package in Precise:
  Incomplete

Bug description:
  On installing Kubuntu alpha 2 candidates I have an error on first boot
  of the installed system.  Plymouth says "waiting for network setup" or
  similar.  I think network-manager is not telling plymouth it has
  started.  By the the time the full system does start network-manager
  works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/924836/+subscriptions