The agent should usually be nm-applet, or the gnome-shell equivalent. There's no real need for gnome-keyring anymore, especially with new connections being system-wide by default (and thus not even needing an agent), unless you set them as not system-wide yourself.
The backtrace could actually tell us a bit more about what NM is trying to achieve, but it's missing big chunks. Could you make sure you have network-manager-gnome-dbgsym or libnm-gtk0-dbgsym installed before you try to reproduce it again? What seems weird to me is that there normally shouldn't be such cases where (have_ap) doesn't exist; since it *has* to be passed by whatever is trying to know about valid security protocols (nm_utils_security_valid checks whether WPA, WPA2, WEP, etc. are supported by your hardware). Maybe there's some other bug you're running into that could explain this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/908516 Title: Dies connecting to wireless with ERROR:nm- utils.c:1231:nm_utils_security_valid: assertion failed: (have_ap) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/908516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
