Public bug reported: Hi,
I am using Ubuntu Precise Mini built with Lightdm and Openbox. $ lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 At first I had wicd, and found that the boot was delayed too much, so I did a search on the web and found this bug report which was looking like the problem I met with: https://bugs.launchpad.net/ubuntu/precise/+source/console- common/+bug/881079 This is how I removed wicd, wicd-gtk... and installed network-manager instead. Then I could not have a connection unless I started it from console with dhclient : "sudo dhclient eth1" (with eth0 it said there was no eth0 interface available). Ok that worked, but still network- manager would not start at boot. So I did again a search on the web and found this thread related to my problem: http://ubuntuforums.org/showpost.php?p=12016190 I followed the advice given, did a downgrade of the said packages and posted about all this here at then end of that thread: http://ubuntuforums.org/showthread.php?p=12361224#post12361224 please read the above post, I have given useful informations found in logs in that one post, and information about packages I have installed, related to network. After I read the first post of that thread I replaced the newer packages with these ones: libnm-glib4_0.9.4.0-0ubuntu3_i386.deb, libnm-glib-vpn1_0.9.4.0-0ubuntu3_i386.deb, libnm-util2_0.9.4.0-0ubuntu3_i386.deb, network-manager_0.9.4.0-0ubuntu3_i386.deb, network-manager-dbg_0.9.4.0-0ubuntu3_i386.deb but the network-manager-gnome has only the latest version available therefore I have these installed at the moment: libnm-gtk-common (0.9.4.1-0ubuntu2) libnm-gtk0 (0.9.4.1-0ubuntu2) network-manager-gnome (0.9.4.1-0ubuntu2) and the packages from the former version of network-manager as mentioned above. The result : now network-manager is started at boot and the wired connection IS AVAILABLE as soon as the desktop is up and running. However I regret that I can still see in the boot sequence the message : "Waiting up to 60 more seconds for network configuration" whereas I have already waited for a bunch of seconds at the message just before "waiting for network configuration". This happens in two machines at home. About the new network-manager : the version number 0.9.4.0-0ubuntu3 has this in the file /etc/init/network-manager.conf: ******************************* # network-manager - network connection manager # # The Network Manager daemon manages the system's network connections, # automatically switching between the best available. description "network connection manager" start on (local-filesystems and started dbus) stop on stopping dbus expect fork respawn script # set $LANG so that messages appearing on the GUI will be translated. See LP: 875017 if [ -r /etc/default/locale ]; then . /etc/default/locale export LANG LANGUAGE LC_MESSAGES LC_ALL fi exec NetworkManager end script ******************************* and after I reinstall the newer packages: ******************************* libnm-glib-vpn1 (version 0.9.4.0-0ubuntu3) sera mis à niveau vers la version 0.9.4.0-0ubuntu4.1 libnm-glib4 (version 0.9.4.0-0ubuntu3) sera mis à niveau vers la version 0.9.4.0-0ubuntu4.1 libnm-util2 (version 0.9.4.0-0ubuntu3) sera mis à niveau vers la version 0.9.4.0-0ubuntu4.1 network-manager (version 0.9.4.0-0ubuntu3) sera mis à niveau vers la version 0.9.4.0-0ubuntu4.1 network-manager-dbg (version 0.9.4.0-0ubuntu3) sera mis à niveau vers la version 0.9.4.0-0ubuntu4.1 ******************************* I noticed there is a new line related to a process needing to be started before network-manager: ****************************** # network-manager - network connection manager # # The Network Manager daemon manages the system's network connections, # automatically switching between the best available. description "network connection manager" start on (local-filesystems and started dbus and static-network-up) stop on stopping dbus expect fork respawn script # set $LANG so that messages appearing on the GUI will be translated. See LP: 875017 if [ -r /etc/default/locale ]; then . /etc/default/locale export LANG LANGUAGE LC_MESSAGES LC_ALL fi exec NetworkManager end script ****************************** which in the "start on" block text is "and static-network-up". I wonder if the problem of network-manager not being started at boot in my install is not due to this line for some reason ? To end with, for any network manager tool, why is there always this incredible delay during the boot due to this long network connection attempt going on ? Here more configuration files, that's bootchart files done with the older network-manager configuation files: http://meets.free.fr/files/bootchart.tar.gz Thanks for giving this bug all the necessary care. I think it might be also considered as a regression. Regards, Mélodie ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: network network-manager precise ubuntu upstart -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
