I've tried that I think, and it didn't help.  I thought we had already
determined that the problem was that network-manager / wpa-supplicant
was choosing the wrong back-end driver.

-- 
[prism2.5] doesn't associate for network-manager with hostap_cs
https://launchpad.net/bugs/57146

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to