network-manager not started at boot after installing Ubuntu Server and then ubuntu-desktop

[komputes]

The network-manager service does not start up automatically at boot. This is only after an update. This seems to affect two machines with different hardware. I've also noticed at boot that on both machines it waits a long time for network configuration.

Steps to reproduce:
1) Install Ubuntu 12.04.1 Server 32-bit
2) Reboot
3) Install ubuntu-desktop
4) Reboot
5) Log in graphically

What happens:
In Unity network-manager does not show up

Expected:
Network Manager should start with the session, nm-applet should be visible.

Workaround:
sudo service network-manager restart

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu4.2
ProcVersionSignature: Ubuntu 3.2.0-36.57-generic-pae 3.2.35
Uname: Linux 3.2.0-36-generic-pae i686
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Jan 22 09:37:07 2013
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
IpRoute:
 default via 192.168.1.254 dev wlan1 proto static
 default dev eth0 scope link metric 1002
 169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.9.64
 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.116 metric 2
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.117 metric 2
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
 seriesoftubes 1 aa949574-af61-4426-9e2e-1d512e30aef3 802-11-wireless 1358868984 Tue 22 Jan 2013 09:36:24 AM CST yes no /org/freedesktop/NetworkManager/Settings/1
 seriesoftubes ffa4f6e0-2fd8-44bc-99c1-301b73a3262a 802-11-wireless 1358868990 Tue 22 Jan 2013 09:36:30 AM CST yes no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/2
 eth0 802-3-ethernet unmanaged /org/freedesktop/NetworkManager/Devices/1
 wlan1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.4.0 connected enabled enabled enabled enabled disabled

[Thomas Hood (jdthood)]

(For future reference) Reading the syslog I see 5 boots.

1. Jan 21 22:25:34

Kernel boots and dhclient starts and gets a reply. Seems that network-manager is not installed yet.

2. Jan 21 22:41:32

Kernel boots and dhclient starts but doesn't get a reply right away. Then there's a "NETDEV WATCHDOG: eth0 (sis900): transmit queue 0 timed out" warning. Then dhclient gets a reply. Then (immediately) NetworkManager starts and fails to configure wlan0, wlan1 and eth0. Interesting error message:

    b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found

3. Jan 21 23:42:29

Kernel boots and dhclient starts but doesn't get a reply .

4. Jan 22 09:03:43

Kernel boots and dhclient starts but doesn't get a reply . Then NetworkManager starts and configures wlan1 and later wlan0.

5. Jan 22 09:24:49

Ditto.

[Thomas Hood (jdthood)]

Do you have connectivity on graphical login, just no indicator in the menu bar?

[komputes (komputes)]

What you see in the logs is from me running "sudo dhclient eth0" manually and "sudo service network-manager restart".

I do not have any connectivity at boot, Network Manager service is stopped at boot. The indicator only shows up after running "sudo service network-manager restart".