Please make sure you don't have any entries in /etc/network/interfaces
that fail to be brought up: any eth*, any wlan*, any bridge
configurations that cannot be brought up will have the boot process hang
until a timeout. This is expected behavior.
NetworkManager has grown a dependency on static-network-up, which is
what brings up the lo interfaces (loopback) also required by
NetworkManager and dnsmasq. This dependency is important and may be a
cause for network-manager (or at least dnsmasq) failing to start. Since
the processes that look at /etc/network/interfaces are the ones
responsible for emitting the static-network-up signal, any invalid
configuration in that file may be cause for delay or network-manager
failing to start.
Please attach the full contents of the file /etc/network/interfaces to
this bug report.
As for network-manager and network-manager-gnome, please make sure to
run the very latest versions available for your release:
sudo apt-get install network-manager/precise network-manager-
gnome/precise libnm-glib4/precise libnm-util2/precise libnm-glib-
vpn1/precise libnm-gtk0/precise libnm-gtk-common/precise
For network-manager and libnm-util*, libnm-glib* you should get versions
0.9.4.0-0ubuntu4.1 (or -0ubuntu4.2 if you have proposed enabled), and
for network-manager-gnome, libnm-gtk* you should get version
0.9.4.1-0ubuntu2.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1080454
Title:
New network-manager is not started at boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1080454/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
