Same problem with gutsy tribe 5. I'll attach the relevant portion of the daemon.log that shows the entire process stalling after stage 2 (device configure) in NetworkManager. However, dhclient fires right after this and before stage 3 (IP configure start) even starts. Unless I'm mistaken, the interface is not up at this point, at least not the IP stack, but dhclient is still started. The ifdown/ifup trick works to bring the interface truly up, so stages 3-5 finish in short order thereafter.
As always, I'll be glad to provide any more details you need. Thanks! ** Attachment added: "daemon.log from affected machine. Interesting stuff starts about line 86." http://launchpadlibrarian.net/9082665/daemon.log -- NetworkManager fails to finish association to AP https://bugs.launchpad.net/bugs/133966 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
