This has been tracked down to a bug in the resolvconf package, causing
/etc/network/if-up.d/000resolvconf to fail and taking the rest of the
ifupdown hooks with it.
We can't create the initial /etc/resolv.conf symlink from the upstart
job when using the live installer, because the job is never run until
boot - and at the time it runs (start on mounted MOUNTPOINT=/run), the
root fs is not writable. So this symlinking *must* be done in the
postinst.
Targeting to beta-1 because we don't want to unsettle this for alpha-2.
** Package changed: ifupdown (Ubuntu Precise) => resolvconf (Ubuntu
Precise)
** Changed in: resolvconf (Ubuntu Precise)
Status: Incomplete => Triaged
** Changed in: resolvconf (Ubuntu Precise)
Milestone: None => ubuntu-12.04-beta-1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/924836
Title:
network-manager does not tell plymouth it has started
Status in “network-manager” package in Ubuntu:
Invalid
Status in “resolvconf” package in Ubuntu:
Triaged
Status in “network-manager” source package in Precise:
Invalid
Status in “resolvconf” source package in Precise:
Triaged
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/network-manager/+bug/924836/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
