NetworkManager hangs starting the service when it is configured for a wireless network which it is not available anymore

[maurizio de santis]

Booting the PC today the Ubuntu screen was blocked at startup time, after a green [OK] and a white blinking underscore.

In recovery mode I figured out the problem: NetworkManager hung trying to connect to a wireless network that wasn't available anymore, and so I couldn't reach the prelogin level.

I can reproduce it in this way:

1) Connect to a wireless network when logged
2) Shutdown the wireless router
3) Reboot

The OS should not show the lightdm screen, but a black screen with a white blinking underscore.

Probably it is reproducible also without rebooting, just with `service NetworkManager restart`, but I didn't tried.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: network-manager 0.9.6.0-0ubuntu7
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
CRDA:
 country IT:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
Date: Mon Oct 22 23:45:55 2012
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IpRoute:
 default via 192.168.1.254 dev wlan0 proto static
 169.254.0.0/16 dev wlan0 scope link metric 1000
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.132 metric 9
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.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
 FASTWEB-1-8MpoA20FNGI0 78f6ec25-2191-4c58-aa59-154b9664116a 802-11-wireless 1350942340 lun 22 ott 2012 23:45:40 CEST yes no /org/freedesktop/NetworkManager/Settings/2
 Connessione via cavo 2 233dae63-9e0e-4887-9b97-b8e6608dddb3 802-3-ethernet 1350940537 lun 22 ott 2012 23:15:37 CEST yes no /org/freedesktop/NetworkManager/Settings/1
 Connessione via cavo 1 a1d97420-fd05-4e5b-9582-736d1beba99e 802-3-ethernet 1350940537 lun 22 ott 2012 23:15:37 CEST yes no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/2
 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1
 eth1 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.6.0 connected enabled enabled enabled enabled disabled

[Mathieu Trudel-Lapierre (cyphermox)]

NetworkManager doesn't block the boot process. If a wireless network isn't available, it will jsut ignore it after a timeout, but the whole thing is done in parallel with the rest of the boot process.

Why do you think this is caused by NetworkManager? What happens in recovery mode?

Could you please attach a screenshot of the screen(s) you see in recovery mode so we have an idea what to look for?

Thanks in advance.

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]