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.
** 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/1070041
Title:
NetworkManager hangs starting the service when it is configured for a
wireless network which it is not available anymore
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1070041/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
