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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924836
Title:
network-manager does not tell plymouth it has started
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/924836/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
