This would indicate it is an upstream bug, after all. Is there anybody able to try the same with Vivid?
I might be wrong, but I don't believe this is wpa-supplicant-related, because there were reports of being able to connect manually with wpa- supplicant, from CLI. So it is most likely NetworkManager's fault... again. But it could also be some change in wpa-supplicant that broke communication between the two. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473088 Title: network manager peap mschapv2 authentication stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1473088/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
